Triple
T35041122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MNSTC-I |
E1011072
|
entity |
| Predicate | coalitionLedBy |
P83371
|
FINISHED |
| Object | United States |
—
|
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: United States | Statement: [MNSTC-I, coalitionLedBy, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coalitionLedBy Context triple: [MNSTC-I, coalitionLedBy, United States]
-
A.
coalitionTalksLedBy
Indicates that discussions or negotiations to form or manage a coalition are being directed or headed by a particular entity.
-
B.
coalitionLed
chosen
Indicates that one entity serves as the primary leader or organizer of a coalition composed of multiple entities.
-
C.
electedPresidentCoalition
Indicates that an entity became president as a result of support from a specific coalition or alliance.
-
D.
candidateCoalition
Indicates a proposed or potential alliance formed between multiple parties or groups, typically for a shared objective such as governing or decision-making.
-
E.
coalitionName
Indicates the designated name or title assigned to a coalition formed by multiple entities.
- 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_69f76dcea02c81908542a223f6d5059f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f785921bd881908979cf85cb13c80a |
completed | May 3, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.