Triple
T36084112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doha Round |
E1043729
|
entity |
| Predicate | majorParticipants |
P33960
|
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: [Doha Round, majorParticipants, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorParticipants Context triple: [Doha Round, majorParticipants, United States]
-
A.
notableParticipant
Indicates that an entity plays a significant or distinguished role as a participant in an event, activity, or context.
-
B.
secondaryParticipants
Indicates that certain entities participate in an event or activity in a supporting or non-primary role alongside the main participants.
-
C.
traditionalParticipants
Indicates that certain entities customarily or historically take part in a particular event, practice, or activity.
-
D.
primaryParticipant
Indicates that an entity plays the main or most central role in a given event, activity, or relationship.
-
E.
mainParties
chosen
Indicates the primary entities that are directly and centrally involved in a given relationship, event, or agreement.
- 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_69f76e3154908190a6f702671c2bea08 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ffacdf9f5c8190baef0245edfe87fc |
completed | May 9, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69ffac5e86e08190a1e6da0840a237ad |
completed | May 9, 2026, 9:51 p.m. |
Created at: May 3, 2026, 4:08 p.m.