Triple
T21499915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ahousaht dialect |
E530447
|
entity |
| Predicate | historicallyOral |
P32654
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Ahousaht dialect, historicallyOral, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyOral Context triple: [Ahousaht dialect, historicallyOral, true]
-
A.
historicallySpoke
Indicates that an entity used a particular language as a spoken language during some period in the past.
-
B.
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.
-
C.
historicallyIn
Indicates that one entity existed, occurred, or was situated within the historical context, period, or jurisdiction associated with another entity.
-
D.
historicalOrigin
Indicates the relationship by which one entity serves as the source, origin, or starting point in history for another entity.
-
E.
historicallySpokenIn
Indicates that a language was used for spoken communication in a particular place or region during a past historical period.
- 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_69e0c45bd15481909fba5910765cdda2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea5ae154819090299773b373b921 |
completed | April 23, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e631f6e68081908f5ee4ce7413803e |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:24 p.m.