Triple
T25715389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London–Sydney |
E644847
|
entity |
| Predicate | isIconicRouteFor |
P43625
|
FINISHED |
| Object | Qantas |
—
|
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: Qantas | Statement: [London–Sydney, isIconicRouteFor, Qantas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isIconicRouteFor Context triple: [London–Sydney, isIconicRouteFor, Qantas]
-
A.
isIconicIn
chosen
Indicates that something is widely recognized as a defining or emblematic example within a particular context, domain, or location.
-
B.
isRouteFor
Indicates that one entity serves as a path, course, or channel used for traveling, transporting, or connecting to another entity.
-
C.
isMajorRouteFor
Indicates that something serves as a primary or heavily used pathway or channel for the movement or flow of something else.
-
D.
isRouteOn
Indicates that one route is located on, follows along, or is aligned with another specified path or infrastructure.
-
E.
isIconicAddressOf
Indicates that one entity is a widely recognized, emblematic, or culturally significant address associated with the other entity.
- 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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fc6211788190bb46c645902c2bc2 |
completed | May 2, 2026, 1:30 p.m. |
| PD | Predicate disambiguation | batch_69f480824a1c81908a8a492eedbc2596 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 9:40 p.m.