Triple
T25715451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BA CityFlyer |
E644849
|
entity |
| Predicate | operatesFromPrimaryHub |
P75285
|
FINISHED |
| Object | London City Airport |
—
|
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: London City Airport | Statement: [BA CityFlyer, operatesFromPrimaryHub, London City Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesFromPrimaryHub Context triple: [BA CityFlyer, operatesFromPrimaryHub, London City Airport]
-
A.
hasPrimaryHub
Indicates that an entity is associated with or operates from a main or central hub location among potentially multiple hubs.
-
B.
operatedHub
Indicates that one entity functions as and manages the operations of a central hub or facility for another entity.
-
C.
previousPrimaryHub
Indicates that an entity served as the main or central hub for another entity at an earlier time, before being replaced by a new primary hub.
-
D.
isCentralHubOf
Indicates that one entity functions as the primary connecting or coordinating hub for activities, resources, or interactions among multiple other entities.
-
E.
primaryHubOfOperator
chosen
Indicates that a given location or facility serves as the main operational hub for a specified operator.
- 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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: April 21, 2026, 9:40 p.m.