Triple
T26947005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taungurung people |
E678673
|
entity |
| Predicate | traditionalStateOrTerritory |
P182822
|
FINISHED |
| Object | Victoria |
—
|
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: Victoria | Statement: [Taungurung people, traditionalStateOrTerritory, Victoria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalStateOrTerritory Context triple: [Taungurung people, traditionalStateOrTerritory, Victoria]
-
A.
stateOrTerritory
Indicates that one entity is a state or territory that is politically or administratively associated with another entity.
-
B.
stateOfTerritory
Indicates the political or administrative state that has authority over a given territory.
-
C.
startStateOrTerritory
Indicates the state or territory in which an event, process, or relationship begins or is initially situated.
-
D.
stateOrRegion
Indicates that one entity is a state or region in which the other entity is located or with which it is associated.
-
E.
borderingStateOrTerritory
Indicates that one state or territory shares a common boundary with another state or territory.
- 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_69eeeb4d69588190a7c912164a1c37b3 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f794f24e588190965e39b77534d53f |
completed | May 3, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
| PDg | Predicate description generation | batch_69f791cad5e08190a8a04ca283dbecaa |
completed | May 3, 2026, 6:19 p.m. |
Created at: April 27, 2026, 6:22 a.m.