Triple
T19941265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ophiotaurus |
E479312
|
entity |
| Predicate | powerCondition |
P137931
|
FINISHED |
| Object | entrails must be burned |
—
|
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: entrails must be burned | Statement: [Ophiotaurus, powerCondition, entrails must be burned]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerCondition Context triple: [Ophiotaurus, powerCondition, entrails must be burned]
-
A.
powerStatus
Indicates whether an entity is currently powered on, off, or in another defined power state.
-
B.
powerOption
Indicates that one entity provides or specifies a particular power-related configuration or choice available to another entity.
-
C.
powerChange
Indicates a change in the level, amount, or state of power associated with an entity over time.
-
D.
powerDuration
Indicates the length of time for which a power, ability, or effect remains active or in force.
-
E.
powersFeature
Indicates that one entity provides the underlying functionality or capability that enables a particular feature of another entity.
- F. None of above. chosen
Provenance (4 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a6318848190a1dd3e0a6fea3fe2 |
completed | April 20, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69e537f47c508190853c4e009c6b5566 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c42c688190a22f4d31ec692377 |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:54 p.m.