Triple
T37154607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woot the Wanderer |
E920458
|
entity |
| Predicate | goesOnQuestWith |
P43670
|
FINISHED |
| Object | Tin Woodman |
—
|
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: Tin Woodman | Statement: [Woot the Wanderer, goesOnQuestWith, Tin Woodman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goesOnQuestWith Context triple: [Woot the Wanderer, goesOnQuestWith, Tin Woodman]
-
A.
objectOfQuest
Indicates that one entity is the target, goal, or item being sought or pursued in another entity’s quest or mission.
-
B.
questGiverIn
Indicates that an entity serves as the quest giver within a specified quest, location, or context.
-
C.
hasAdventureOn
Indicates that an entity participates in or experiences an adventure that takes place on or during a specified context, such as a time, location, or medium.
-
D.
questInvolvedIn
chosen
Indicates that an entity participates in, is associated with, or plays a role in a particular quest or mission.
-
E.
consequenceOfQuest
Indicates that an event, state, or outcome occurs as a direct result of completing or progressing in a specific quest.
- 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_69f76e9f87c08190b4c8f7fafbd8345a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:15 p.m.