Triple
T6892907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yorta Yorta language |
E159091
|
entity |
| Predicate | AIATSISCode |
P73981
|
FINISHED |
| Object | D2 |
—
|
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: D2 | Statement: [Yorta Yorta language, AIATSISCode, D2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AIATSISCode Context triple: [Yorta Yorta language, AIATSISCode, D2]
-
A.
tribalCode
Indicates that an entity is governed by, associated with, or identified according to a specific tribal legal or regulatory code.
-
B.
ICCCode
Indicates that an entity is associated with a specific International Criminal Court (ICC) code, identifying its classification or legal reference under ICC standards.
-
C.
iauCode
Indicates the standardized code assigned by the International Astronomical Union (IAU) to uniquely identify an astronomical object or entity.
-
D.
ianaIdentifierType
Indicates that one entity specifies the type or category of an IANA (Internet Assigned Numbers Authority) identifier associated with another entity.
-
E.
isocodeCategory
Indicates that an entity is classified under a specific ISO code category or grouping.
- 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_69c6883568c8819081db6407e892cccc |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d930ab548190953291d63cbc721b |
completed | March 27, 2026, 7:23 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b53e9881909ec298daa9f1913b |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d8c48ba48190b8d3aa7b8d22816b |
completed | March 27, 2026, 7:21 p.m. |
Created at: March 27, 2026, 2:24 p.m.