Triple
T10286539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Winkies |
E241241
|
entity |
| Predicate | primaryOccupationAfterWitch |
P75487
|
FINISHED |
| Object | subjects of the Tin Woodman |
—
|
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: subjects of the Tin Woodman | Statement: [Winkies, primaryOccupationAfterWitch, subjects of the Tin Woodman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryOccupationAfterWitch Context triple: [Winkies, primaryOccupationAfterWitch, subjects of the Tin Woodman]
-
A.
memberLaterOccupation
chosen
Indicates that an individual later held a particular occupation or position after an earlier point in time or role.
-
B.
subjectOccupation
Indicates that the subject holds or performs a particular job, profession, or role as their occupation.
-
C.
endedOccupationOf
Indicates that one entity brought another entity’s occupation or control of a place or position to an end.
-
D.
resumedOccupation
Indicates that an entity has returned to and continued a previous occupation or role after a period of interruption or absence.
-
E.
earlierOccupation
Indicates that one occupation held by an entity occurred before another occupation in that entity’s work history.
- 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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f117708190928f92ae2611d724 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:40 a.m.