Triple
T3649131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chimariko language |
E77374
|
entity |
| Predicate | hasDocumentationType |
P19006
|
FINISHED |
| Object | word lists |
—
|
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: word lists | Statement: [Chimariko language, hasDocumentationType, word lists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDocumentationType Context triple: [Chimariko language, hasDocumentationType, word lists]
-
A.
hasDocumentationStatus
Indicates the current state or condition of documentation associated with an entity, such as whether it exists, is complete, or is up to date.
-
B.
hasDocumentationAt
Indicates that something is documented or described in a specific document, file, or location.
-
C.
documentationType
chosen
Indicates the specific category or kind of documentation associated with or required for an entity or process.
-
D.
documentTypeIncluded
Indicates that a particular document type is contained within, or is part of, a specified set or collection of document types.
-
E.
hasDocumentClass
Indicates that an entity is associated with, or categorized under, a specific class or type of document.
- 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_69ad85de1b988190a45f8dbfebc806fc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc38c22548190a271a69fb832a5a8 |
completed | March 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69adb8445b2c8190ab07f6ad4e010d0e |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:24 p.m.