Triple
T2810414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garden Court |
E54153
|
entity |
| Predicate | hasArchitecturalEra |
P22153
|
FINISHED |
| Object | early 1900s |
—
|
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: early 1900s | Statement: [Garden Court, hasArchitecturalEra, early 1900s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArchitecturalEra Context triple: [Garden Court, hasArchitecturalEra, early 1900s]
-
A.
locatedInHistoricPeriod
Indicates that an entity exists, occurs, or is situated within a specific historic period or era.
-
B.
appliesToEra
Indicates that something is relevant, valid, or in effect during a particular historical or temporal era.
-
C.
partOfEra
Indicates that one entity exists as a temporal segment or component within the duration or scope of a larger historical era.
-
D.
eraOfMajorConstruction
chosen
Indicates the time period during which the primary or most significant phase of construction for an entity took place.
-
E.
architectureHistory
Indicates a historical or developmental relationship between an entity and its architectural evolution, style, or significant architectural events over time.
- 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_69ab49dcee188190b5c6eca9ae9e3469 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde335b38819090c70d5e2ca14d79 |
completed | March 7, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69abdd0740208190911dc9c9546a79ae |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:59 p.m.