Triple
T20475472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Wizard and I |
E502306
|
entity |
| Predicate | characterState |
P110763
|
FINISHED |
| Object | Elphaba is optimistic |
—
|
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: Elphaba is optimistic | Statement: [The Wizard and I, characterState, Elphaba is optimistic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterState Context triple: [The Wizard and I, characterState, Elphaba is optimistic]
-
A.
definesStateCharacter
Indicates that something specifies or determines the essential qualities or characteristics of a state or condition.
-
B.
titleCharacterState
chosen
Indicates the state or condition a character is in within the context of a specific title or work.
-
C.
character3
Indicates a tertiary or additional character role associated with an entity, typically the third distinct character linked within a given context or work.
-
D.
character2
Indicates that a second character entity is involved in the relationship or context defined by the predicate.
-
E.
character1
Indicates that the subject is identified as the first or primary character in a narrative or context.
- 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_69e0b4ae5f1081908768b0c9a3a0bf38 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6996464448190bdf9cf63c736d6dd |
completed | April 20, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69e5768372988190b08ef8ae67d42ab6 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:34 a.m.