Triple
T5492595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cherokee language |
E123735
|
entity |
| Predicate | syllabaryCreationPeriod |
P1436
|
FINISHED |
| Object | early 19th century |
—
|
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: early 19th century | Statement: [Cherokee language, syllabaryCreationPeriod, early 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: syllabaryCreationPeriod Context triple: [Cherokee language, syllabaryCreationPeriod, early 19th century]
-
A.
hasSyllabary
Indicates that one entity possesses or is associated with a specific syllabary writing system used to represent its language or notation.
-
B.
writingSystemDevelopedFrom
Indicates that one writing system originated, evolved, or was derived from another earlier writing system.
-
C.
deciphermentYear
Indicates the year in which something (typically a script, code, or inscription) was successfully deciphered or interpreted.
-
D.
hasWritingTraditionSince
chosen
Indicates that a writing tradition has been present or established for an entity starting from a specified point in time.
-
E.
languageOfEarliestForm
Indicates the language in which the earliest known form or attested version of something (e.g., a text, name, or expression) is recorded.
- 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_69bd464a2d908190869324ce176779c8 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9280403c8190baaa3f7923449a37 |
completed | March 20, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69bd91a8df6481908d1643f7342fe6f0 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:10 p.m.