Triple
T35875592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arthur D. Story |
E1037349
|
entity |
| Predicate | hasArchitectOrBuilder |
P95351
|
FINISHED |
| Object | L. A. Dunton |
—
|
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: L. A. Dunton | Statement: [Arthur D. Story, hasArchitectOrBuilder, L. A. Dunton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArchitectOrBuilder Context triple: [Arthur D. Story, hasArchitectOrBuilder, L. A. Dunton]
-
A.
hasArchitectRole
Indicates that an entity holds or fulfills the role or function of an architect in relation to another entity or project.
-
B.
hasArchitectGroup
Indicates that an entity is associated with, or designed by, a particular group of architects.
-
C.
hasRelationToArchitect
chosen
Indicates that one entity has a specified relationship or association with an architect.
-
D.
hasArchitectNotability
Indicates that an entity is notable or recognized specifically for its work or role as an architect.
-
E.
isArchitectDesigned
Indicates that something was created or planned by a professional architect.
- 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_69f76e1e701c8190a4990d4978ce4fe6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe610e1f6881908f10070ba64643cf |
completed | May 8, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69fe604c6c008190ad659e9b9fa82f7b |
completed | May 8, 2026, 10:14 p.m. |
Created at: May 3, 2026, 4:06 p.m.