Triple
T27997058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Kemp Starley |
E707040
|
entity |
| Predicate | headquartersLocationOfFoundedCompany |
P164004
|
FINISHED |
| Object | Coventry |
—
|
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: Coventry | Statement: [John Kemp Starley, headquartersLocationOfFoundedCompany, Coventry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headquartersLocationOfFoundedCompany Context triple: [John Kemp Starley, headquartersLocationOfFoundedCompany, Coventry]
-
A.
headquartersLocationOfFoundedOrganization
Indicates that a location serves as the headquarters of an organization that was founded there.
-
B.
headquartersFoundedAt
Indicates that an organization's headquarters was originally established at a specific location.
-
C.
headquartersLocation
Indicates the place where an organization’s main administrative center or principal office is located.
-
D.
headquartersFoundedCompanyIn
Indicates that a headquarters entity established or founded a particular company.
-
E.
foundingLocationOfFoundedOrganization
Indicates the place where an organization was originally established or founded.
- 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_69ef96b980d88190a753b2f9a978595a |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6416fbf4081909b0913c337927fc4 |
completed | May 2, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 27, 2026, 7:54 p.m.