Triple
T6489481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Republic Airways |
E147997
|
entity |
| Predicate | focusCityRole |
P71023
|
FINISHED |
| Object | feeds traffic into major airline hubs |
—
|
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: feeds traffic into major airline hubs | Statement: [Republic Airways, focusCityRole, feeds traffic into major airline hubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusCityRole Context triple: [Republic Airways, focusCityRole, feeds traffic into major airline hubs]
-
A.
urbanRole
Indicates the function, status, or role that an entity holds within an urban or city context.
-
B.
hasCityRole
Indicates that an entity holds or is assigned a specific role, function, or status within a particular city.
-
C.
hasMajorCityRole
Indicates that an entity plays a significant official or functional role in the governance, administration, or key operations of a major city.
-
D.
ethnicRole
Indicates a role, function, or social position that is specifically associated with or defined by an entity’s ethnicity.
-
E.
hasUrbanRole
Indicates that an entity plays a specific functional or social role within an urban or city context.
- F. None of above. chosen
Provenance (4 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_69c009088f3081909cd467b05919de30 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06a9926fc81909db0f390e385e97d |
completed | March 22, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69c06740bebc81909d9d6956baa2bcb9 |
completed | March 22, 2026, 10:03 p.m. |
| PDg | Predicate description generation | batch_69c067f1ef148190bc0355abe83f7e16 |
completed | March 22, 2026, 10:06 p.m. |
Created at: March 22, 2026, 4:52 p.m.