Triple
T2643731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fairy Godmother |
E62936
|
entity |
| Predicate | conditionOnMagic |
P29885
|
FINISHED |
| Object | magic ends at midnight |
—
|
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: magic ends at midnight | Statement: [Fairy Godmother, conditionOnMagic, magic ends at midnight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conditionOnMagic Context triple: [Fairy Godmother, conditionOnMagic, magic ends at midnight]
-
A.
triggerCondition
chosen
Indicates the specific circumstances or state under which an associated event, action, or process is initiated or activated.
-
B.
coreCondition
Indicates that something serves as the primary or fundamental condition that must hold for a situation, process, or relationship to apply.
-
C.
hasCondition
Indicates that an entity possesses, experiences, or is affected by a particular condition or state.
-
D.
conditionForRecognition
Indicates that one entity specifies the requirement or circumstance under which another entity is acknowledged, accepted, or officially recognized.
-
E.
typeOfMagic
Indicates that one entity is a specific category, school, or kind of magic associated with another entity.
- 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_69ab4c3f2dcc819082df80f5e032f690 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abd90046dc81908bab3440733f1e98 |
completed | March 7, 2026, 7:51 a.m. |
| PD | Predicate disambiguation | batch_69abd814298c8190952f05aed43f6bb8 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.