Triple
T2309281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Na-Dene |
E51913
|
entity |
| Predicate | hasDocumentationStatus |
P39118
|
FINISHED |
| Object | varies by language |
—
|
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: varies by language | Statement: [Na-Dene, hasDocumentationStatus, varies by language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDocumentationStatus Context triple: [Na-Dene, hasDocumentationStatus, varies by language]
-
A.
hasDocumentationAt
Indicates that something is documented or described in a specific document, file, or location.
-
B.
hasOfficialDocument
Indicates that an entity possesses or is associated with a formal, authorized document issued by a recognized authority.
-
C.
documentedBy
Indicates that something is recorded, described, or evidenced in a specific document or set of documents.
-
D.
hasLimitedDocumentation
Indicates that the subject is associated with documentation that is sparse, incomplete, or not sufficiently detailed.
-
E.
legacyDocumentedBy
Indicates that information about a legacy item or concept is recorded or described in a specific documenting source.
- 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_69a88b0bb30c81908ded03b006d29387 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abce1f4f0c8190a714e4dcb8449f7e |
completed | March 7, 2026, 7:05 a.m. |
| PD | Predicate disambiguation | batch_69abc58ce2a081908ce2f0cadd92e9f8 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abce1e7c788190a15890feb2437f1d |
completed | March 7, 2026, 7:05 a.m. |
Created at: March 4, 2026, 7:49 p.m.