Triple
T29386704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snufkin |
E745272
|
entity |
| Predicate | oftenDepartsTo |
P109232
|
FINISHED |
| Object | the south |
—
|
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: the south | Statement: [Snufkin, oftenDepartsTo, the south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenDepartsTo Context triple: [Snufkin, oftenDepartsTo, the south]
-
A.
departsFrom
Indicates that an entity (such as a vehicle, person, or process) begins its movement, journey, or operation starting from a specified location or point of origin.
-
B.
hasDepartureTo
chosen
Indicates that a departure event originates from one place and is directed toward a specific destination.
-
C.
departureTime
Indicates the specific time at which an entity leaves or begins its departure from a location or state.
-
D.
followsDepartureOf
Indicates that one event or action occurs after and in sequence with the departure of another entity or event.
-
E.
hasMainPortOfDeparture
Indicates that an entity uses a specified port as its primary location for beginning journeys or departures.
- 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_69f0a79cfd5481909b4dde750cb8d2c6 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 28, 2026, 2:39 p.m.