Triple
T13089260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cheyenne orthography |
E310416
|
entity |
| Predicate | usesApostropheFor |
P64285
|
FINISHED |
| Object | glottal stop |
—
|
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: glottal stop | Statement: [Cheyenne orthography, usesApostropheFor, glottal stop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesApostropheFor Context triple: [Cheyenne orthography, usesApostropheFor, glottal stop]
-
A.
isWrittenWithApostrophe
chosen
Indicates that something (typically a word, phrase, or name) is written using an apostrophe character as part of its spelling or punctuation.
-
B.
usesAnaphora
Indicates that one entity refers back to another previously mentioned entity using anaphoric expression (e.g., pronouns or repeated phrases).
-
C.
usesWord
Indicates that one entity employs, contains, or makes use of a particular word in its expression, content, or communication.
-
D.
usedWithSurname
Indicates that something (typically a given name or title) is used together with a particular surname in naming or reference.
-
E.
usesAbbreviationIn
Indicates that an entity is referred to by an abbreviated form within a specified context, source, or representation.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d98138a1d481908a139f2f67eb3472 |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:03 p.m.