Triple
T622146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Horn sea route |
E14535
|
entity |
| Predicate | distanceCharacteristic |
P17802
|
FINISHED |
| Object | much longer than overland routes to California |
—
|
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: much longer than overland routes to California | Statement: [Cape Horn sea route, distanceCharacteristic, much longer than overland routes to California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceCharacteristic Context triple: [Cape Horn sea route, distanceCharacteristic, much longer than overland routes to California]
-
A.
distance
Indicates the spatial separation or length between two points, objects, or locations.
-
B.
distanceCategory
Indicates the qualitative classification of how far apart two entities are from each other (e.g., near, medium, far).
-
C.
flightDistance
Indicates the measured distance covered by a flight between its origin and destination.
-
D.
distanceFromTerminus
Indicates the measured distance of an entity from a defined endpoint or terminus along a route, path, or sequence.
-
E.
distanceFromDowntown
Indicates the physical distance between a given location and the central downtown area.
- 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_69a4934b17c881909ace8270e8ddd202 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e402d9c8190936896e3ebb6edc5 |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49d0069d0819087c83b608f6fc053 |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49e2107548190af0c1d67cfa475d1 |
completed | March 1, 2026, 8:14 p.m. |
Created at: March 1, 2026, 7:35 p.m.