Triple
T34216062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Florida |
E877790
|
entity |
| Predicate | hadInternationalRoutesTo |
P151540
|
FINISHED |
| Object | London |
—
|
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 | Statement: [Air Florida, hadInternationalRoutesTo, London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadInternationalRoutesTo Context triple: [Air Florida, hadInternationalRoutesTo, London]
-
A.
majorInternationalRoutesTo
Indicates that there are significant, globally important transportation routes (such as air, sea, or land corridors) connecting one location to another.
-
B.
hasInternationalDestinations
chosen
Indicates that an entity offers, includes, or is connected to destinations located in foreign countries.
-
C.
hasSeaRouteConnection
Indicates that there exists a navigable maritime route linking two locations or entities.
-
D.
hasInternationalPort
Indicates that an entity possesses a port facility that supports international transportation or trade connections.
-
E.
hasInternationalDestinationType
Indicates that something is associated with a type or category of international destination.
- 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.