Triple
T37985037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adnyamathanha |
E947664
|
entity |
| Predicate | hasOralHistory |
P32654
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Adnyamathanha, hasOralHistory, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOralHistory Context triple: [Adnyamathanha, hasOralHistory, yes]
-
A.
hasRichOralTradition
chosen
Indicates that an entity is associated with a longstanding, culturally significant body of stories, histories, or knowledge transmitted primarily through spoken word rather than written texts.
-
B.
hasOralDisc
Indicates that an entity possesses an oral disc, i.e., a specialized circular or disc-like mouth region used for feeding or attachment.
-
C.
earlierOralMaterialFrom
Indicates that the subject is derived from or based on earlier oral material provided by the object.
-
D.
historicallySpoke
Indicates that an entity used a particular language as a spoken language during some period in the past.
-
E.
isMemorizedOrally
Indicates that the information, content, or material is retained and transmitted through oral memorization rather than written or recorded forms.
- 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_69f76ef8a1d08190a741bbbc5970e3b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff2d22ffb48190ae58ddf3c7e02869 |
completed | May 9, 2026, 12:48 p.m. |
| PD | Predicate disambiguation | batch_69ff2ac2e1c4819096cc64e94aef2ff0 |
completed | May 9, 2026, 12:38 p.m. |
Created at: May 3, 2026, 4:20 p.m.