Triple
T35922589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | regent honeyeater |
E1038925
|
entity |
| Predicate | historicalRangeIncluded |
P132119
|
FINISHED |
| Object | South Australia |
—
|
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: South Australia | Statement: [regent honeyeater, historicalRangeIncluded, South Australia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalRangeIncluded Context triple: [regent honeyeater, historicalRangeIncluded, South Australia]
-
A.
historicalRangeIncludes
chosen
Indicates that the temporal span or period associated with one entity encompasses the historical time range of another entity.
-
B.
historicalRange
Indicates the time period over which something existed, was active, or was relevant in history.
-
C.
historicalRangeType
Indicates the specific kind or category of historical time span or period associated with an entity or event.
-
D.
hasHistoryPeriod
Indicates that something is associated with, belongs to, or occurs within a specific historical period or era.
-
E.
containsHistoricPeriod
Indicates that one entity encompasses or includes a specific historic period within its temporal or contextual scope.
- 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_69f76e2320748190b7f5c4750d0cd0d3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00ca5e907481909d391afd55938a1b |
completed | May 10, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_6a00ca2214348190a674a85ede709e2e |
completed | May 10, 2026, 6:10 p.m. |
Created at: May 3, 2026, 4:07 p.m.