Triple
T35978567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wazhazhe (Osage) people |
E1040490
|
entity |
| Predicate | hasWrittenSystem |
P184302
|
FINISHED |
| Object | modern Osage orthography |
—
|
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: modern Osage orthography | Statement: [Wazhazhe (Osage) people, hasWrittenSystem, modern Osage orthography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWrittenSystem Context triple: [Wazhazhe (Osage) people, hasWrittenSystem, modern Osage orthography]
-
A.
isWritten
Indicates that a text, document, or content has been created or recorded in written form by an agent.
-
B.
hasWrittenFor
Indicates that one entity has created written content (such as articles, stories, or texts) for or on behalf of another entity, typically a publication, organization, or platform.
-
C.
writtenTo
Indicates that something has been addressed or directed in written form to a particular recipient.
-
D.
hasWrittenRecordsIn
Indicates that an entity has produced or maintains written records in a specified medium, format, or location.
-
E.
hasWrittenForSeries
Indicates that an entity has authored or contributed written content for a particular series.
- 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_69f76e27758c81909b711cf38a130aaf |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ad15f3b88190b7c9742a734fec5f |
completed | May 3, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69f7acad20388190b9b10270ca9bdfbc |
completed | May 3, 2026, 8:14 p.m. |
Created at: May 3, 2026, 4:07 p.m.