Triple
T26675871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DIL |
E672453
|
entity |
| Predicate | operatesInternationalRoutes |
P151540
|
FINISHED |
| Object | Australia |
—
|
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: Australia | Statement: [DIL, operatesInternationalRoutes, Australia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesInternationalRoutes Context triple: [DIL, operatesInternationalRoutes, Australia]
-
A.
operatesInternationally
Indicates that the entity conducts activities or business across national borders in multiple countries.
-
B.
majorInternationalRoutesTo
Indicates that there are significant, globally important transportation routes (such as air, sea, or land corridors) connecting one location to another.
-
C.
hasInternationalDestinations
chosen
Indicates that an entity offers, includes, or is connected to destinations located in foreign countries.
-
D.
isOneOfBusiestInternationalRoutes
Indicates that a route ranks among the most heavily used or frequently traveled international connections.
-
E.
operatesShortHaulRoutes
Indicates that an entity (such as an airline or transport operator) runs or provides short-distance routes or services.
- 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_69eecda13424819092b17942c4edf722 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
Created at: April 27, 2026, 3:16 a.m.