Triple
T16604934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ALP National Conference |
E403424
|
entity |
| Predicate | partyFamily |
P57232
|
FINISHED |
| Object | Labor parties in Australia |
—
|
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: Labor parties in Australia | Statement: [ALP National Conference, partyFamily, Labor parties in Australia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partyFamily Context triple: [ALP National Conference, partyFamily, Labor parties in Australia]
-
A.
familyEvent
Indicates a relationship where an event is organized around or significantly involves members of a family, such as gatherings, celebrations, or milestones.
-
B.
party
Indicates that an entity participates as a side or participant in an event, agreement, or situation.
-
C.
partyCategory
chosen
Indicates the classification or type assigned to a party within a given context or system.
-
D.
family
Indicates a familial relationship or connection between entities, such as being related by blood, marriage, or adoption.
-
E.
familyAspect
Indicates a relationship where one entity is characterized by a particular familial role, status, or aspect in relation to another entity.
- 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3608ff1a481909084e7ad984b0f95 |
completed | April 18, 2026, 10:44 a.m. |
| PD | Predicate disambiguation | batch_69e296aabc508190b3836a91b49113ad |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.