Triple
T13089265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cheyenne orthography |
E310416
|
entity |
| Predicate | primaryCase |
P107988
|
FINISHED |
| Object | lowercase |
—
|
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: lowercase | Statement: [Cheyenne orthography, primaryCase, lowercase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryCase Context triple: [Cheyenne orthography, primaryCase, lowercase]
-
A.
primaryFor
Indicates that one entity serves as the main or principal option, resource, or association for another entity among possible alternatives.
-
B.
primaryFront
Indicates that one entity serves as the main or most important front-facing side or surface in relation to another entity.
-
C.
primaryIssue
Indicates that the related item is the main or most important issue among a set of issues.
-
D.
primarySin
Indicates a fundamental or chief moral wrongdoing attributed to an entity, often viewed as the root or most significant sin in a given context.
-
E.
primaryCharge
Indicates that one charge is designated as the main or most significant charge associated with an entity or case, typically among multiple possible charges.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69d98114a6508190b1e8e018bb5a068c |
completed | April 10, 2026, 11 p.m. |
Created at: April 9, 2026, 9:03 p.m.