Triple
T33845960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Division of Kingsford Smith |
E867478
|
entity |
| Predicate | hasBeenHeldByParty |
P95512
|
FINISHED |
| Object | Australian Labor Party |
—
|
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: Australian Labor Party | Statement: [Division of Kingsford Smith, hasBeenHeldByParty, Australian Labor Party]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeenHeldByParty Context triple: [Division of Kingsford Smith, hasBeenHeldByParty, Australian Labor Party]
-
A.
hasBeenHeldBy
chosen
Indicates that an entity has previously possessed, controlled, or occupied another entity for some duration in the past.
-
B.
hasPreviouslyBeenHeldIn
Indicates that an entity was located, confined, or kept in a particular place or container at some time in the past.
-
C.
heldOf
Indicates that something is possessed, controlled, or kept by a particular entity.
-
D.
hasHeldBy
Indicates that one entity has been physically or conceptually grasped, possessed, or kept in the control of another entity.
-
E.
heldForParty
Indicates that something was organized, hosted, or conducted for the benefit or occasion of a particular party or group.
- 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_69f349937b648190a34ada70f6a2b534 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 1, 2026, 1:47 a.m.