Triple
T12772135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Cenerentola |
E305270
|
entity |
| Predicate | omitsElement |
P3119
|
FINISHED |
| Object | fairy godmother |
—
|
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: fairy godmother | Statement: [La Cenerentola, omitsElement, fairy godmother]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: omitsElement Context triple: [La Cenerentola, omitsElement, fairy godmother]
-
A.
mayBeOmittedWhen
Indicates that one element is allowed to be left out or excluded under certain conditions defined by another element or context.
-
B.
excludedFrom
Indicates that one entity is deliberately not included within the scope, membership, or applicability of another entity or set.
-
C.
excludes
chosen
Indicates that one entity deliberately omits, leaves out, or does not allow the inclusion of another entity within a set, group, or context.
-
D.
excludesPhase
Indicates that one entity explicitly omits, leaves out, or does not include a particular phase or stage within a process or lifecycle.
-
E.
doesNotConsider
Indicates that one entity fails or chooses not to take another entity or factor into account when forming judgments, decisions, or actions.
- 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.