Triple
T2113345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TPA |
E42552
|
entity |
| Predicate | hasNumberOfParties |
P34865
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [TPA, hasNumberOfParties, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfParties Context triple: [TPA, hasNumberOfParties, 3]
-
A.
hasMajorParties
Indicates that an entity is associated with its primary participating parties or main involved groups.
-
B.
hasOppositionParties
Indicates that an entity (typically a government or ruling body) has one or more political parties that formally oppose or challenge its policies or authority.
-
C.
hasMajorityPartyMembers
Indicates that a group, body, or organization contains more members from a particular political party than from any other party, giving that party majority representation.
-
D.
hasMinorityPartyMembers
Indicates that the subject includes or is associated with members belonging to a minority political party.
-
E.
mainParties
Indicates the primary entities that are directly and centrally involved in a given relationship, event, or agreement.
- F. None of above. chosen
Provenance (4 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_69a8871040f08190aac2e2d0ab6b47ad |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbb0495d0819097dc936540743b74 |
completed | March 7, 2026, 5:43 a.m. |
| PD | Predicate disambiguation | batch_69abb7ba08948190a3c236bb53ee4257 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb85fe7a08190b991b1f23bc34f93 |
completed | March 7, 2026, 5:32 a.m. |
Created at: March 4, 2026, 7:43 p.m.