Triple
T36692759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eve |
E906003
|
entity |
| Predicate | disobeyedCommandOf |
P176578
|
FINISHED |
| Object | God |
—
|
NE NERFINISHED |
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: God | Statement: [Eve, disobeyedCommandOf, God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disobeyedCommandOf Context triple: [Eve, disobeyedCommandOf, God]
-
A.
commandedAgainst
Indicates that one entity issued an order or directive opposing, targeting, or in conflict with another entity.
-
B.
commandedAgainstBy
Indicates that an entity is the target or object of a command issued by another entity, specifying who is commanded against whom.
-
C.
resistedOrderTo
chosen
Indicates that one entity refused to comply with or actively opposed an order given by another entity.
-
D.
commandedTo
Indicates that one entity has issued an order or directive for another entity to perform a specific action or fulfill a particular duty.
-
E.
commandedOperationAgainst
Indicates that one entity issued authoritative orders to initiate or conduct a specific military or strategic operation directed against 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_69f76e70d2448190bdd3ce781ba971c5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c7e778a08190a9c943ce798902af |
completed | May 3, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69f7c4796ebc819084a0dc08505e5f14 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:12 p.m.