Triple
T17096721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pánfilo de Narváez expedition of 1528 |
E414867
|
entity |
| Predicate | distanceTraveledOverland |
P16230
|
FINISHED |
| Object | thousands of kilometers |
—
|
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: thousands of kilometers | Statement: [Pánfilo de Narváez expedition of 1528, distanceTraveledOverland, thousands of kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceTraveledOverland Context triple: [Pánfilo de Narváez expedition of 1528, distanceTraveledOverland, thousands of kilometers]
-
A.
distanceTraveled
chosen
Indicates the total length of the path an entity has moved over a period of time or between two points.
-
B.
traveledFor
Indicates that an entity moved or journeyed to a place or event for a specific purpose, reason, or activity.
-
C.
trailDistanceContext
Indicates the contextual distance or separation between entities along a trail, path, or route.
-
D.
trailDistanceApprox
Indicates that the distance along a trail between two locations is approximately a specified value, allowing for some margin of error.
-
E.
tourLength
Indicates the total duration or distance covered by a tour or route.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbfe92988190aa066745ca9791d5 |
completed | April 18, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69e35d67b14481909fcdbdeaa5c34785 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.