Triple
T18327375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1949 Australian federal election |
E439045
|
entity |
| Predicate | compulsoryEnrollment |
P130777
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [1949 Australian federal election, compulsoryEnrollment, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compulsoryEnrollment Context triple: [1949 Australian federal election, compulsoryEnrollment, yes]
-
A.
enrollment
Indicates the formal act of registering or being registered in a course, program, or institution, establishing an official participant–provider relationship.
-
B.
enrolledIn
Indicates that one entity is formally registered as a participant in a course, program, or institution represented by another entity.
-
C.
usesEnrollment
Indicates that one entity employs or relies on a particular enrollment record, process, or status in order to function or be applied.
-
D.
compulsoryEducation
Indicates that an entity is legally required to participate in a specified level or period of formal education.
-
E.
compulsoryMembershipFrom
Indicates that one entity is required or mandated to hold membership in another entity.
- 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50aac14488190840b9c22209f13d1 |
completed | April 19, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69e44fe4ee10819086b4142444fca1f5 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a1bda48190a9cd1db436d4be62 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:36 a.m.