Triple
T28933888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jim (Adventures of Huckleberry Finn) |
E733860
|
entity |
| Predicate | journeySetting |
P160924
|
FINISHED |
| Object | Mississippi River |
—
|
NE NERFINISHED |
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: Mississippi River | Statement: [Jim (Adventures of Huckleberry Finn), journeySetting, Mississippi River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: journeySetting Context triple: [Jim (Adventures of Huckleberry Finn), journeySetting, Mississippi River]
-
A.
journeyDestination
Indicates that one entity serves as the endpoint or intended destination of another entity’s journey or travel.
-
B.
settingOfTravels
chosen
Indicates that a location serves as the setting or backdrop for a character’s travels or journey.
-
C.
journeyFrom
Indicates that an entity undertakes or originates a journey starting from a specified location or source.
-
D.
journey
Indicates that an entity travels or moves from one place or state to another, typically over a period of time or distance.
-
E.
travelRouteContext
Indicates the contextual details (such as purpose, conditions, or circumstances) under which a particular travel route is taken or defined.
- 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_69f05b0b49b08190b8994b339c7980f6 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65b5453d0819082d3783b3b11019a |
completed | May 2, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 8:30 a.m.