Triple
T3200217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Challenger |
E67030
|
entity |
| Predicate | distanceTravelled |
P16230
|
FINISHED |
| Object | about 68,000 nautical miles |
—
|
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: about 68,000 nautical miles | Statement: [HMS Challenger, distanceTravelled, about 68,000 nautical miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceTravelled Context triple: [HMS Challenger, distanceTravelled, about 68,000 nautical miles]
-
A.
distanceTraveled
chosen
Indicates the total length of the path an entity has moved over a period of time or between two points.
-
B.
distance
Indicates the spatial separation or length between two points, objects, or locations.
-
C.
wentToDistance
Indicates that an entity traveled to or reached a specified distance from a reference point.
-
D.
hasApproximateDrivingDistanceFrom
Indicates that one entity is located at an estimated or approximate driving distance from another entity, typically measured along road routes rather than as a precise or exact value.
-
E.
flightDistance
Indicates the measured distance covered by a flight between its origin and 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_69ad8589bd988190afa7ed2bdffb7b33 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada9ad4b1c8190bc6ad0f025f238c8 |
completed | March 8, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69ad9e05e4f48190adbe4366cdba2349 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:07 p.m.