Triple
T34465972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sabadell Airport |
E884767
|
entity |
| Predicate | usesRunwayNumbering |
P8866
|
FINISHED |
| Object | 13 |
—
|
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: 13 | Statement: [Sabadell Airport, usesRunwayNumbering, 13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRunwayNumbering Context triple: [Sabadell Airport, usesRunwayNumbering, 13]
-
A.
usesRunwayNumberingConvention
Indicates that an airport or runway follows a specific standardized system for assigning runway identification numbers.
-
B.
hasRunwayNumber
chosen
Indicates that an airport or airfield runway is assigned a specific identifying number.
-
C.
hasRunwayNumberRange
Indicates that an entity (such as an airport or airfield) has runways whose identification numbers fall within a specified numeric range.
-
D.
usesRunwayAlternation
Indicates that runway usage is alternated between different runways or runway directions according to a defined pattern or schedule.
-
E.
runwayFormat
Indicates the specific physical configuration or layout type of a runway used for takeoff and landing.
- 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_69f349c73a94819094dfcf50d00620b8 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 1, 2026, 2:01 a.m.