Triple
T17076021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Humboldt’s travel journals |
E414349
|
entity |
| Predicate | endOfDocumentedTravels |
P125758
|
FINISHED |
| Object | 1804 |
—
|
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: 1804 | Statement: [Humboldt’s travel journals, endOfDocumentedTravels, 1804]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfDocumentedTravels Context triple: [Humboldt’s travel journals, endOfDocumentedTravels, 1804]
-
A.
travelsOn
Indicates that an entity moves or journeys using a particular route, path, or mode of transportation.
-
B.
traveledAs
Indicates that an entity moved from one place to another in the role, capacity, or identity specified by another entity (e.g., as a tourist, as a representative, as a refugee).
-
C.
tourEndCountry
Indicates the country in which a tour or journey concludes.
-
D.
travelsThrough
Indicates that something moves along, passes across, or is routed via a particular path, medium, or location.
-
E.
documentsJourneyTo
Indicates that one entity records or describes the travel, route, or progression of another entity from one place or state to another.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbc47808819088a4ca039689b213 |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d642f74819098c014135e249b27 |
completed | April 18, 2026, 10:31 a.m. |
| PDg | Predicate description generation | batch_69e3753f93c88190808fec5692f66699 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:34 a.m.