Triple
T36050036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CAD4 |
E1042780
|
entity |
| Predicate | identifiesAirportInRegion |
P17216
|
FINISHED |
| Object | British Columbia |
—
|
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: British Columbia | Statement: [CAD4, identifiesAirportInRegion, British Columbia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identifiesAirportInRegion Context triple: [CAD4, identifiesAirportInRegion, British Columbia]
-
A.
otherRegionalAirports
Indicates that the entities are airports located in different regions from each other but considered as alternative or comparable regional airports.
-
B.
airportIdentifier
Indicates that an entity is identified by a specific airport code or designation within an aviation identification system.
-
C.
hasRegionalAirport
chosen
Indicates that a place or region possesses or is served by a regional airport.
-
D.
airportRecognition
Indicates that an entity formally acknowledges, identifies, or designates another entity as an airport.
-
E.
isMajorRegionalAirportFor
Indicates that an airport serves as a primary or significant air travel hub for a particular region.
- 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_69f76e2e41f8819091f9fb0536920fec |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:07 p.m.