Triple
T1079132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ǀXam |
E23906
|
entity |
| Predicate | primaryDocumentationType |
P19006
|
FINISHED |
| Object | ethnographic records |
—
|
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: ethnographic records | Statement: [ǀXam, primaryDocumentationType, ethnographic records]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryDocumentationType Context triple: [ǀXam, primaryDocumentationType, ethnographic records]
-
A.
primarySources
Indicates that one entity serves as an original, authoritative source of information or evidence for another entity.
-
B.
documentationType
chosen
Indicates the specific category or kind of documentation associated with or required for an entity or process.
-
C.
documentTypeProduced
Indicates that one entity produces, generates, or creates a document of a specified type.
-
D.
primaryReference
Indicates that one entity serves as the main or authoritative source of information or citation for another entity.
-
E.
foundingDocument
Indicates that one entity serves as the official charter, constitution, or primary legal/organizational document that establishes or defines the other entity.
- 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_69a493f1ddf48190a99d54b00e99f8ce |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b943b41481909b24050ca7e78971 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b73d9f08819093668104f129840e |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.