Triple
T12771822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The House at Pooh Corner |
E305263
|
entity |
| Predicate | hasCharacterDeparture |
P46825
|
FINISHED |
| Object | Christopher Robin leaves for school |
—
|
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: Christopher Robin leaves for school | Statement: [The House at Pooh Corner, hasCharacterDeparture, Christopher Robin leaves for school]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCharacterDeparture Context triple: [The House at Pooh Corner, hasCharacterDeparture, Christopher Robin leaves for school]
-
A.
hasDepartureSide
Indicates the side or direction from which an entity departs or leaves a location.
-
B.
departureFromSeries
Indicates that an entity stops being part of, or exits from, a particular series or sequence.
-
C.
hasDepartureEnd
Indicates that an entity marks the endpoint or final location of a departure event or journey.
-
D.
hasEmbarkedPersonnel
Indicates that one entity has taken personnel on board or loaded them for transport or deployment.
-
E.
departsFrom
chosen
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.
- 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_69d7bdf2b43c819098ae5aa68e61ea58 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96df5b68481908a5d40516b09be52 |
completed | April 10, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69d96409739881909174ba005a986cb5 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:28 p.m.