Triple
T35540587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southampton–New York City |
E1027047
|
entity |
| Predicate | countryAtEasternTerminus |
P56160
|
FINISHED |
| Object | United Kingdom |
E732
|
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: United Kingdom | Statement: [Southampton–New York City, countryAtEasternTerminus, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryAtEasternTerminus Context triple: [Southampton–New York City, countryAtEasternTerminus, United Kingdom]
-
A.
easternTerminusCountry
chosen
Indicates the country in which the eastern terminus (end point) of something, such as a route or infrastructure, is located.
-
B.
easternTerminusAtBorderWith
Indicates that something’s eastern endpoint or final location lies at, or directly on, a border shared with another entity.
-
C.
easternmostPartOf
Indicates that one entity is the geographically furthest-east portion or segment of another entity.
-
D.
easternTerminusRegion
Indicates the region in which something (such as a route, line, or path) has its eastern endpoint or terminus.
-
E.
governingCountryOnEast
Indicates that a country exercises governmental authority or control over a territory or region located to its east.
- 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_69f76e008ba08190927acd8e5e0344c8 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a01d7b3ce8c8190b2f90be730505765 |
completed | May 11, 2026, 1:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a386831cf288190b86792ac8025cd4d |
completed | June 21, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_6a01d5115a6c8190a6d9f96ec484135a |
completed | May 11, 2026, 1:09 p.m. |
Created at: May 3, 2026, 4:04 p.m.