Triple
T36525412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koori Mail |
E900287
|
entity |
| Predicate | hasControlModel |
P204916
|
FINISHED |
| Object | Indigenous-controlled |
—
|
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: Indigenous-controlled | Statement: [Koori Mail, hasControlModel, Indigenous-controlled]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasControlModel Context triple: [Koori Mail, hasControlModel, Indigenous-controlled]
-
A.
hasControlElement
Indicates that one entity includes or is associated with a component specifically intended to control, regulate, or influence its behavior or operation.
-
B.
hasControlService
Indicates that one entity provides or performs a control-related service for another entity.
-
C.
hasAccessModel
Indicates that one entity is permitted to use, interact with, or retrieve a particular model controlled by another entity or system.
-
D.
hasControlFields
Indicates that one entity possesses or defines control-related parameters, settings, or fields that govern the behavior or configuration of another entity or process.
-
E.
hasModelIn
Indicates that an entity is represented or instantiated as a model within a specified context, system, or container.
- 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_69f76e5eedb88190a393b8c623f71dd7 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:11 p.m.