Triple
T26115752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EGCN |
E658819
|
entity |
| Predicate | associatedAirportCounty |
P197874
|
FINISHED |
| Object | South Yorkshire |
—
|
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: South Yorkshire | Statement: [EGCN, associatedAirportCounty, South Yorkshire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedAirportCounty Context triple: [EGCN, associatedAirportCounty, South Yorkshire]
-
A.
associatedAirport
Indicates a relationship where an entity is linked or connected to a specific airport, typically as its relevant or corresponding airport.
-
B.
associatedAirportServes
Indicates that a given airport provides service to, or is used by, the associated entity (such as a city, region, or facility).
-
C.
associatedAirportCountrySubdivision
Indicates the specific country subdivision (such as a state, province, or region) in which the associated airport is located.
-
D.
hasAirportWithinJurisdiction
Indicates that a governing authority or administrative region has legal or administrative control over an airport located within its boundaries.
-
E.
associatedAirportStateOrUT
Indicates that an airport is located within or linked to a specific state or union territory.
- 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_69ee5bc20298819099a42be042eb2349 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69feb5e66224819083b87c3707a5a5e0 |
completed | May 9, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_69feb3bd700c8190991ed200cd3c04db |
completed | May 9, 2026, 4:10 a.m. |
| PDg | Predicate description generation | batch_69feb5e50a7481908d6bff55bd85e06d |
completed | May 9, 2026, 4:19 a.m. |
Created at: April 26, 2026, 8:05 p.m.