Triple
T18903369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian federal electoral divisions |
E462391
|
entity |
| Predicate | minimumNumberOfDivisionsPerOriginalState |
P1905
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [Australian federal electoral divisions, minimumNumberOfDivisionsPerOriginalState, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minimumNumberOfDivisionsPerOriginalState Context triple: [Australian federal electoral divisions, minimumNumberOfDivisionsPerOriginalState, 5]
-
A.
hasNumberOfDivisions
chosen
Indicates the relationship that specifies how many divisions or subunits an entity possesses.
-
B.
divisionSize
Indicates the size or magnitude of a division or subdivided part in relation to a whole.
-
C.
lastDivisionNumber
Indicates the numerical identifier assigned to the most recent division in a sequence or hierarchy of divisions.
-
D.
parallelDivision
Indicates that one entity is divided or partitioned in a way that runs parallel to the division or partitioning of another entity.
-
E.
divisionFrequency
Indicates how often a division event occurs within a given context or time frame.
- 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_69d8dcfd05bc819088903cca13cc2846 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c52b07c08190be0db22826462ae3 |
completed | April 20, 2026, 6:18 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e27e1481908a8da10b28f07875 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.