Triple
T32075688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Missenden Road |
E819139
|
entity |
| Predicate | hasCountryResidenceAtTerminus |
P79353
|
FINISHED |
| Object | Chequers |
E131415
|
NE 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: Chequers | Statement: [Missenden Road, hasCountryResidenceAtTerminus, Chequers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCountryResidenceAtTerminus Context triple: [Missenden Road, hasCountryResidenceAtTerminus, Chequers]
-
A.
hasBranchResidenceIn
Indicates that an organization maintains a branch or subsidiary located in a specified place or jurisdiction.
-
B.
hasResidenceIn
Indicates that an entity lives or maintains a primary dwelling in a specified location.
-
C.
hasTraditionalResidenceCountry
chosen
Indicates that an entity’s customary or long-term country of residence is the specified country.
-
D.
hasResidenceOn
Indicates that one entity’s place of residence is located on or along another entity, such as a street, road, or other linear feature.
-
E.
hasResidency
Indicates that an entity holds an official, legally recognized residential status in a particular place or jurisdiction.
- F. None of above.
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_69f348ff8ef88190931c08ba530a36bc |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a0358c946f08190a8fb41c643074475 |
completed | May 12, 2026, 4:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2f0bbbc5c081908ff2c294b5851e35 |
completed | June 14, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_6a03586e5bb08190a71e075fde7cd679 |
completed | May 12, 2026, 4:42 p.m. |
Created at: May 1, 2026, 12:23 a.m.