Triple
T19144206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Division of Fraser (ACT) |
E468636
|
entity |
| Predicate | isFederal |
P23390
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Division of Fraser (ACT), isFederal, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFederal Context triple: [Division of Fraser (ACT), isFederal, true]
-
A.
federalStatus
chosen
Indicates that an entity holds a particular legal or administrative status under federal (national) authority or jurisdiction.
-
B.
canBeFederalizedBy
Indicates that an entity has the legal or practical capacity to be brought under the authority, control, or jurisdiction of a specified federal-level entity.
-
C.
federalAffiliation
Indicates a formal relationship in which an entity is associated with, governed by, or part of a federal-level organization or authority.
-
D.
locatedInFederalEntity
Indicates that one entity is geographically or administratively situated within the jurisdiction or boundaries of a specified federal entity.
-
E.
includesFederalState
Indicates that one entity encompasses or contains both federal-level and state-level components, jurisdictions, or elements.
- 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_69d8dd084ff48190ac0f8c46ee722629 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e977fa208190aa8cafd0966599c6 |
completed | April 20, 2026, 8:53 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b475d88190a8c15e8eb01dbfef |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:06 p.m.