Triple
T10120705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Chute |
E223278
|
entity |
| Predicate | roleAtStrawberryHill |
P92085
|
FINISHED |
| Object | architectural adviser |
—
|
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: architectural adviser | Statement: [John Chute, roleAtStrawberryHill, architectural adviser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtStrawberryHill Context triple: [John Chute, roleAtStrawberryHill, architectural adviser]
-
A.
roleAtMidway
Indicates that an entity holds or held a specific role, position, or function at the midpoint or intermediate stage of a process, event, or time period.
-
B.
roleAtSavoIsland
Indicates the specific role, position, or function an entity held in relation to the event or context associated with Savo Island.
-
C.
roleAtVine
Indicates that an entity holds or held a specific role or position at the company Vine.
-
D.
roleAsPlace
Indicates that an entity functions or is used as a place or location in relation to another entity or event.
-
E.
roleAtWaterloo
Indicates the specific position, function, or capacity an entity held in relation to the Battle of Waterloo.
- F. None of above. chosen
Provenance (4 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_69ca8422047c81909d66b717b8b18cf3 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cdd266b18c8190b35fe637c912e756 |
completed | April 2, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba1d360819087698d04a53cc87e |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4fed19d481909d2c7ff1114664b6 |
completed | April 1, 2026, 5:03 p.m. |
Created at: March 30, 2026, 9:04 p.m.