Triple
T25497791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mason City |
E639026
|
entity |
| Predicate | hasWorkOfArchitect |
P95351
|
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: [Mason City, hasWorkOfArchitect, Frank Lloyd Wright]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkOfArchitect Context triple: [Mason City, hasWorkOfArchitect, Frank Lloyd Wright]
-
A.
hasRelationToArchitect
chosen
Indicates that one entity has a specified relationship or association with an architect.
-
B.
relatedWorkOfArchitect
Indicates that one work is related to, associated with, or otherwise connected in context or authorship to an architect.
-
C.
hasLandmarkArchitect
Indicates that a landmark is associated with, or was designed by, a specific architect.
-
D.
architecturalWork
Indicates that one entity is an architectural creation (such as a building or structure) designed or realized by another entity.
-
E.
hasArchitectNotability
Indicates that an entity is notable or recognized specifically for its work or role as an 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_69e75dbbd2a88190b70e1e645de14b9a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 21, 2026, 2:41 p.m.