Triple
T34278970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Independent Presbyterian Church (Savannah) |
E879538
|
entity |
| Predicate | hasPhysicalStructure |
P134317
|
FINISHED |
| Object | church building |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: church building | Statement: [Independent Presbyterian Church (Savannah), hasPhysicalStructure, church building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhysicalStructure Context triple: [Independent Presbyterian Church (Savannah), hasPhysicalStructure, church building]
-
A.
hasHumanStructure
Indicates that one entity possesses or exhibits a structural form or organization characteristic of humans.
-
B.
hasPhysicalNature
Indicates that one entity possesses or exhibits a specific physical form, composition, or material nature in relation to another.
-
C.
haveStructure
chosen
Indicates that an entity possesses a particular internal organization, arrangement, or structural composition.
-
D.
hasNoPhysicalBody
Indicates that an entity exists or operates without a tangible, material, or corporeal form.
-
E.
hasOrganStructure
Indicates that one entity possesses, contains, or is characterized by a particular organ structure.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f349b5f6648190b9420d94a4cd16e0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 1, 2026, 1:57 a.m.