Triple
T2122247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tregami language |
E43949
|
entity |
| Predicate | hasScriptStatus |
P35264
|
FINISHED |
| Object | primarily unwritten |
—
|
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: primarily unwritten | Statement: [Tregami language, hasScriptStatus, primarily unwritten]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScriptStatus Context triple: [Tregami language, hasScriptStatus, primarily unwritten]
-
A.
containsScript
Indicates that one entity includes or embeds the script of another entity within it.
-
B.
hasScriptHistory
Indicates that an entity is associated with a record or chronology of scripts or writing systems it has used or been represented in over time.
-
C.
programStatus
Indicates the current state or condition of a program within its lifecycle (e.g., planned, active, paused, completed, or terminated).
-
D.
scripturalStatus
Indicates the relationship between a text and its recognition or classification as scriptural, canonical, or authoritative within a religious or doctrinal tradition.
-
E.
hasEditorScripting
Indicates that an entity provides or supports scripting capabilities specifically for editing or editor-related functionality.
- 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_69a88717cfe48190b7ecdd68c824848a |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbb51e8088190a1aeafee4e8dff63 |
completed | March 7, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69abb7bd86cc8190938ef06c1ed6d969 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb895d11881908345032595a679ba |
completed | March 7, 2026, 5:33 a.m. |
Created at: March 4, 2026, 7:44 p.m.