Triple
T16322197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | England–Australia maritime route |
E396322
|
entity |
| Predicate | alternativePath |
P19868
|
FINISHED |
| Object | route via Cape of Good Hope |
—
|
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: route via Cape of Good Hope | Statement: [England–Australia maritime route, alternativePath, route via Cape of Good Hope]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alternativePath Context triple: [England–Australia maritime route, alternativePath, route via Cape of Good Hope]
-
A.
alternativeRoute
chosen
Indicates that there exists a different path or option that can be taken instead of the primary or original route.
-
B.
alternativePlan
Indicates that one plan serves as a substitute or backup option for another plan within the same context or objective.
-
C.
trailAlternativeName
Indicates that an entity (such as a trail) is known by an alternative or secondary name.
-
D.
alternativeForm
Indicates that one entity is an alternative version, variant, or representation of another entity.
-
E.
alternateMode
Indicates that one entity functions as an alternative form, configuration, or mode of operation for another 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e296b706108190b43a05b784633050 |
completed | April 17, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69e219fc72c881909d452274e7af8238 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.