Triple
T11931243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Division |
E283914
|
entity |
| Predicate | positionRelativeToTopFlight |
P102229
|
FINISHED |
| Object | below the First Division |
—
|
LITERAL 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: below the First Division | Statement: [Second Division, positionRelativeToTopFlight, below the First Division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionRelativeToTopFlight Context triple: [Second Division, positionRelativeToTopFlight, below the First Division]
-
A.
positionOnFlight
Indicates the specific seat or positional assignment that an entity has on a particular flight.
-
B.
aircraftHeight
Indicates the vertical distance or altitude of an aircraft relative to a reference level (such as ground or sea level).
-
C.
hasRelativePositionAtAirport
Indicates that one entity has a specific spatial or positional relationship to another entity within the context or layout of an airport.
-
D.
locatedAtAltitude
Indicates that an entity exists or is positioned at a specific height above a reference level, typically sea level.
-
E.
locationRelativeToPitch
Indicates the spatial position of an entity in relation to the pitch (e.g., above, beside, or within the pitch area).
- 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_69d6ab2ce9c48190b5d39511b524f666 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d90303a9a88190a4044e6310ba9b4b |
completed | April 10, 2026, 2:02 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3af0188190bfb22be5c97b3349 |
completed | April 10, 2026, 8:56 a.m. |
| PDg | Predicate description generation | batch_69d8d399d58c81908dab572aa82426d7 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 8, 2026, 9:45 p.m.