Triple
T32075695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Missenden Road |
E819139
|
entity |
| Predicate | countryResidenceServed |
P201871
|
FINISHED |
| Object | Chequers |
—
|
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: Chequers | Statement: [Missenden Road, countryResidenceServed, Chequers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryResidenceServed Context triple: [Missenden Road, countryResidenceServed, Chequers]
-
A.
destinationCountryServed
Indicates that a given entity (such as a service, route, or provider) serves or operates to a specified destination country.
-
B.
hasCountryServed
Indicates that a person or organization has provided service to, or performed duties on behalf of, a specified country.
-
C.
countryOfCapitalServed
Indicates the country in which a given capital city serves as the official seat of government.
-
D.
primaryCountryServed
Indicates the main country that is primarily served or targeted by an entity’s activities, services, or operations.
-
E.
countrySubdivisionServed
Indicates a relationship where a service, organization, or entity operates within and provides its offerings to a specific administrative region or subdivision of a country.
- 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_69f348ff8ef88190931c08ba530a36bc |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a002dd4066c8190945a09ed82f44f3f |
completed | May 10, 2026, 7:03 a.m. |
| PD | Predicate disambiguation | batch_6a002b141f4081909999e14988105f3a |
completed | May 10, 2026, 6:52 a.m. |
| PDg | Predicate description generation | batch_6a002dd3294881909e860157fc459a85 |
completed | May 10, 2026, 7:03 a.m. |
Created at: May 1, 2026, 12:23 a.m.