Triple
T24915255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurubarabulu |
E623964
|
entity |
| Predicate | sourceContext |
P18207
|
FINISHED |
| Object | early colonial accounts of Sydney |
—
|
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: early colonial accounts of Sydney | Statement: [Kurubarabulu, sourceContext, early colonial accounts of Sydney]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceContext Context triple: [Kurubarabulu, sourceContext, early colonial accounts of Sydney]
-
A.
originContext
chosen
Indicates the situational or environmental circumstances from which an entity, event, or piece of information originates.
-
B.
source
Indicates that something originates from, is derived from, or is provided by a particular entity or location.
-
C.
sourceCategory
Indicates the classification or type from which something originates or is derived.
-
D.
supplyContext
Indicates that one entity provides relevant background information or situational details that clarify or frame another entity, action, or statement.
-
E.
sourceState
Indicates the original or starting state from which a transition, change, or process begins.
- 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_69e2fac889c081908e9ff686cb428e5a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cf017a88190b4985b11159c907d |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 5:28 a.m.