Triple
T12804090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Klamath Ethnography |
E306097
|
entity |
| Predicate | documentedTopics |
P24066
|
FINISHED |
| Object | kinship among the Klamath |
—
|
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: kinship among the Klamath | Statement: [Klamath Ethnography, documentedTopics, kinship among the Klamath]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentedTopics Context triple: [Klamath Ethnography, documentedTopics, kinship among the Klamath]
-
A.
coveredTopics
Indicates that certain subjects or themes have been addressed or included within a discussion, document, or activity.
-
B.
documentationTopic
Indicates that one entity serves as the subject or focus of documentation related to another entity.
-
C.
includesTopics
chosen
Indicates that one entity contains, covers, or addresses the specified topics as part of its content or scope.
-
D.
featuresTopic
Indicates that something (such as a work, event, or item) prominently includes, focuses on, or is organized around a particular topic.
-
E.
documentedThrough
Indicates that something is recorded, evidenced, or made known by means of a specific document or documentation process.
- 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e7e3be48190ba9159c9f1ac2ccd |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d9640ed7448190b276e7fab649f7d2 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:30 p.m.