Triple
T28494899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cher |
E721079
|
entity |
| Predicate | hasScriptCodeRole |
P29840
|
FINISHED |
| Object | identifies Cherokee script in metadata |
—
|
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: identifies Cherokee script in metadata | Statement: [Cher, hasScriptCodeRole, identifies Cherokee script in metadata]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScriptCodeRole Context triple: [Cher, hasScriptCodeRole, identifies Cherokee script in metadata]
-
A.
hasScriptCode
Indicates that an entity is associated with a particular writing system identified by a specific script code.
-
B.
hasScriptCodeStatus
Indicates the status or condition assigned to a script code within a given coding or classification system.
-
C.
scriptCodeRole
chosen
Indicates the role or function that a particular script code plays within a given context or system.
-
D.
containsScript
Indicates that one entity includes or embeds the script of another entity within it.
-
E.
hasScriptBy
Indicates that one entity has its script authored, written, or created by another entity.
- 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_69f01a5afdac8190ac6e72d5c100bd58 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 28, 2026, 3:03 a.m.