Triple
T33845766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MDC–T (Khupe faction) |
E867474
|
entity |
| Predicate | hasMainRivalFaction |
P53524
|
FINISHED |
| Object | MDC–T (Chamisa faction) |
—
|
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: MDC–T (Chamisa faction) | Statement: [MDC–T (Khupe faction), hasMainRivalFaction, MDC–T (Chamisa faction)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainRivalFaction Context triple: [MDC–T (Khupe faction), hasMainRivalFaction, MDC–T (Chamisa faction)]
-
A.
hasOpposingFaction
chosen
Indicates that one faction stands in opposition or conflict to another faction.
-
B.
hasMajorFaction
Indicates that an entity possesses or is associated with a primary or dominant faction within a given context.
-
C.
mainRivalAlliance
Indicates that one alliance is considered the primary or most significant rival of another alliance.
-
D.
hasForeignRival
Indicates that an entity has at least one rival that is based in or originates from a different country or foreign jurisdiction.
-
E.
hasFaction
Indicates that an entity is affiliated with, belongs to, or is represented by a particular faction or group.
- 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_69f349937b648190a34ada70f6a2b534 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a0143a4ab3c8190a240b0facfe130a9 |
completed | May 11, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_6a01426b2d4481908654bfa4a02c457d |
completed | May 11, 2026, 2:43 a.m. |
Created at: May 1, 2026, 1:47 a.m.