Triple
T791683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newcastle Airport |
E16927
|
entity |
| Predicate | isRegionalHub |
P9422
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Newcastle Airport, isRegionalHub, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRegionalHub Context triple: [Newcastle Airport, isRegionalHub, true]
-
A.
isRegionalPort
Indicates that a port serves primarily a specific region or local area rather than functioning as a major national or international hub.
-
B.
isCommercialHubIn
chosen
Indicates that a place functions as a primary center of commercial or business activity within a specified larger area or region.
-
C.
Global HubLocation
Indicates a location that serves as a central, primary hub for global operations, connections, or activities.
-
D.
isResidentialHubIn
Indicates that a location functions primarily as a residential center or hub within a specified larger area or region.
-
E.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
- 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_69a4936cb7448190914f5fe4b8d81607 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a798c7608190b9c79c52a1fe0859 |
completed | March 1, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69a4a50ef72c819084ffe9f31dbd0262 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:38 p.m.