Triple
T34491833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Larkin Building |
E885487
|
entity |
| Predicate | hasFurnishingsDesigner |
P89588
|
FINISHED |
| Object | Frank Lloyd Wright |
—
|
NE NERFINISHED |
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: Frank Lloyd Wright | Statement: [Larkin Building, hasFurnishingsDesigner, Frank Lloyd Wright]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFurnishingsDesigner Context triple: [Larkin Building, hasFurnishingsDesigner, Frank Lloyd Wright]
-
A.
decorationDesigner
Indicates that one entity is the person or agent responsible for designing the decoration of another entity.
-
B.
interiorDecoratedBy
chosen
Indicates that the interior of a space or structure has been designed or decorated by a specific agent or entity.
-
C.
hasNotableInteriorDesigner
Indicates that an entity has a notable interior designer responsible for designing or significantly influencing its interior spaces.
-
D.
designerAlias
Indicates that one name or label is used as an alternative alias for a designer.
-
E.
designerOccupation
Indicates that one entity serves as the professional designer or design specialist for another entity.
- 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_69f349cafcec8190997b45b3fdc16c27 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:01 a.m.