Triple
T4139218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Party of Australia – NSW |
E89231
|
entity |
| Predicate | roleInCoalition |
P6756
|
FINISHED |
| Object | junior partner |
—
|
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: junior partner | Statement: [National Party of Australia – NSW, roleInCoalition, junior partner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInCoalition Context triple: [National Party of Australia – NSW, roleInCoalition, junior partner]
-
A.
allianceRole
chosen
Indicates the specific function, status, or responsibility an entity holds within an alliance or cooperative partnership.
-
B.
roleInCouncil
Indicates that an entity holds a specific position or function within a council or governing body.
-
C.
roleAtD.C.United
Indicates that an entity holds or held a specific role or position within the D.C. United soccer organization.
-
D.
roleInMissions
Indicates the specific function, duty, or position an entity holds within one or more missions.
-
E.
memberOfPoliticalCoalition
Indicates that an entity belongs to or participates as a constituent member in a specific political coalition.
- 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_69aed95785788190ae75bcf0cd1cafdf |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03a0f3408190adba7a8513bd3d12 |
completed | March 9, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69af018a54848190987f18c066c75068 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:43 p.m.