Triple
T10497537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pau Pyrénées Airport |
E247577
|
entity |
| Predicate | hasFlightScope |
P56356
|
FINISHED |
| Object | regional |
—
|
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: regional | Statement: [Pau Pyrénées Airport, hasFlightScope, regional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFlightScope Context triple: [Pau Pyrénées Airport, hasFlightScope, regional]
-
A.
flightScope
chosen
Indicates a relationship where the extent, range, or coverage of a flight (such as its route, duration, or operational limits) is specified or constrained.
-
B.
isFlownOn
Indicates that an entity (such as a person or object) travels or is transported using a particular aircraft or airline as the means of flight.
-
C.
hasSpinnaker
Indicates that an entity is equipped with or possesses a spinnaker sail.
-
D.
fliesFlag
Indicates that one entity displays or hoists the flag of another entity, symbolically representing affiliation, identity, or allegiance.
-
E.
hasLockFlight
Indicates that one entity is associated with a specific lock flight, representing a relationship where the entity uses, contains, or is located at that sequence of canal locks.
- F. None of above.
Provenance (3 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_69d381c309b88190af78aa681cf6a4c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5098d8ac481909c4adedbc4ad1c03 |
completed | April 7, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8e24ac8190912c9f11b8bd3084 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:25 p.m.