Triple
T5721190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frank Lloyd Wright Home and Studio |
E126148
|
entity |
| Predicate | significantRebuildOrExpansionYear |
P61916
|
FINISHED |
| Object | 1895 |
—
|
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: 1895 | Statement: [Frank Lloyd Wright Home and Studio, significantRebuildOrExpansionYear, 1895]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantRebuildOrExpansionYear Context triple: [Frank Lloyd Wright Home and Studio, significantRebuildOrExpansionYear, 1895]
-
A.
rebuiltOrExpanded
chosen
Indicates that one entity has been reconstructed, enlarged, or otherwise significantly developed from its previous form or state.
-
B.
reconstructionYear
Indicates the year in which something was rebuilt, restored, or reconstructed after damage, alteration, or destruction.
-
C.
reconstructionOrRestorationDate
Indicates the date on which an entity was reconstructed or restored after damage, alteration, or deterioration.
-
D.
renovationYear
Indicates the year in which an entity underwent renovation or significant refurbishment.
-
E.
yearBuilt
Indicates the specific year in which something (typically a structure or object) was constructed or completed.
- 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_69c0082e3d548190950169847b43043b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029014588819094a2a0f6f9b66bab |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021c47f4c81909e6849c3be3e951c |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:46 p.m.