Triple
T298247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | forty-niners |
E6139
|
entity |
| Predicate | travelRoutes |
P3034
|
FINISHED |
| Object | overland trails across North America |
—
|
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: overland trails across North America | Statement: [forty-niners, travelRoutes, overland trails across North America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: travelRoutes Context triple: [forty-niners, travelRoutes, overland trails across North America]
-
A.
tourismRegion
Indicates that a place or area is designated or recognized as a tourism region associated with another geographic or administrative entity.
-
B.
transportCorridor
chosen
Indicates a route or pathway used to move people, goods, or resources between locations.
-
C.
touringActivity
Indicates an activity where an entity travels from place to place, typically for visiting, performing, or sightseeing purposes.
-
D.
touristAttractionIn
Indicates that a place functions as a tourist attraction located within a specified geographic area or entity.
-
E.
placesWithin
Indicates that one place or area is located entirely inside the boundaries of another place or area.
- 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_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea4778cc8190be7b648a82542891 |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e937af888190a0960708f09ae033 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.