Triple
T34216066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Florida |
E877790
|
entity |
| Predicate | mainFocusCity |
P1655
|
FINISHED |
| Object | Orlando |
—
|
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: Orlando | Statement: [Air Florida, mainFocusCity, Orlando]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainFocusCity Context triple: [Air Florida, mainFocusCity, Orlando]
-
A.
servesAsFocusCityFor
chosen
Indicates that a city functions as a primary or designated focus city for an airline, organization, or transportation network, typically hosting significant but not hub-level operations or activities.
-
B.
primaryCity
Indicates that one city serves as the main or most important city associated with a given region, entity, or context.
-
C.
principalCityOf
Indicates that a city serves as the main or most important city (often administrative, economic, or cultural center) of a specified region or area.
-
D.
motherCityOf
Indicates that one city is considered the primary, originating, or foundational city in relation to another city, often as its source, protector, or central authority.
-
E.
cityOn
Indicates that a city is geographically located on a specified landform, area, or administrative 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_69f349b0b4bc819088c1552424089ee9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7107e66e88190a799e0c78f1af117 |
completed | May 3, 2026, 9:08 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:55 a.m.