Triple
T4386689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Matrix Revolutions |
E99259
|
entity |
| Predicate | featuresConflictBetween |
P4897
|
FINISHED |
| Object | humans |
—
|
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: humans | Statement: [The Matrix Revolutions, featuresConflictBetween, humans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresConflictBetween Context triple: [The Matrix Revolutions, featuresConflictBetween, humans]
-
A.
reportedConflict
Indicates that one party has formally reported the existence of a conflict involving another party or situation.
-
B.
conflictWith
chosen
Indicates that two entities are in opposition or disagreement, such that their goals, actions, or states are incompatible or interfere with each other.
-
C.
conflictedBetween
Indicates being torn or uncertain between two or more options, positions, or commitments.
-
D.
supportedConflict
Indicates that one party provided assistance, resources, or endorsement to a side involved in a conflict or dispute.
-
E.
conflictRequirement
Indicates that one requirement is incompatible with or prevents the fulfillment of another requirement.
- 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_69b3454f739481909ff6c28331f0c0b9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b352669f608190b3aa7030d8073e04 |
completed | March 12, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69b34f572efc8190bad1e5078cbcb75a |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:19 p.m.