Triple
T36567533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koori |
E902018
|
entity |
| Predicate | usedAsSelfIdentifier |
P28298
|
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: [Koori, usedAsSelfIdentifier, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsSelfIdentifier Context triple: [Koori, usedAsSelfIdentifier, true]
-
A.
usedAsSelfDesignation
chosen
Indicates that an entity is used by a person or group as a term to refer to or identify themselves.
-
B.
mayUseSelfIdentification
Indicates that an entity is permitted to rely on its own self-declared identity or attributes for a given purpose or context.
-
C.
identifiedUsing
Indicates that one entity was recognized, distinguished, or determined by means of a specified method, tool, or identifier.
-
D.
identityUsedBy
Indicates that a particular identity is being employed or utilized by a specific entity.
-
E.
usedAsAuthorityFor
Indicates that one entity is relied upon as an authoritative source or reference for validating, justifying, or supporting another entity.
- 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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fed83b1d188190a318b0ad3003200a |
completed | May 9, 2026, 6:46 a.m. |
| PD | Predicate disambiguation | batch_69fed78e03548190b6e6ad93ae8d131d |
completed | May 9, 2026, 6:43 a.m. |
Created at: May 3, 2026, 4:11 p.m.