Triple
T36391359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carter Hall |
E896334
|
entity |
| Predicate | hasBuildingPlan |
P10988
|
FINISHED |
| Object | central hall plan |
—
|
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: central hall plan | Statement: [Carter Hall, hasBuildingPlan, central hall plan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuildingPlan Context triple: [Carter Hall, hasBuildingPlan, central hall plan]
-
A.
hasArchitecturalPlanType
Indicates that an entity has or is associated with a specific type or category of architectural plan.
-
B.
hasBuildingFrom
Indicates a relationship where a location or site possesses or includes a building that originates from, or was constructed in, a specified time period, source, or context.
-
C.
hasBuildingStatus
Indicates the current condition, classification, or operational state assigned to a building.
-
D.
containsBuilding
Indicates that one location or area includes a building within its boundaries.
-
E.
hasPlan
chosen
Indicates that an entity possesses or is associated with a specific plan or course of action.
- 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_69f76e52e3108190becf70b090ae7bd6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: May 3, 2026, 4:10 p.m.