Triple
T25715368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London–Sydney |
E644847
|
entity |
| Predicate | historicallyRequiredMultipleStops |
P175947
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [London–Sydney, historicallyRequiredMultipleStops, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyRequiredMultipleStops Context triple: [London–Sydney, historicallyRequiredMultipleStops, true]
-
A.
hasStops
Indicates that a route, service, or journey includes one or more intermediate stopping points at specified locations.
-
B.
numberOfIntermediateStops
Indicates the count of stops or pauses that occur between the starting point and the final destination in a journey or process.
-
C.
requiresJourneyOf
Indicates that one entity can only be achieved, accessed, or completed by undertaking a journey or progression involving another entity.
-
D.
hasStopoverState
Indicates that an entity’s journey or process includes an intermediate stop or temporary state before reaching its final destination or outcome.
-
E.
hasHistoricalRoute
Indicates that an entity possesses or is associated with a route that has historical significance or origin.
- F. None of above. chosen
Provenance (4 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_69f6db3606808190a80c6e9f5da5b33e |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6db1bc348819097c844f76e2fa4fe |
completed | May 3, 2026, 5:20 a.m. |
Created at: April 21, 2026, 9:40 p.m.