Triple
T32797711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kushite pantheon |
E838810
|
entity |
| Predicate | hasScriptUsedInCult |
P81935
|
FINISHED |
| Object | Meroitic script |
—
|
NE NERFINISHED |
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: Meroitic script | Statement: [Kushite pantheon, hasScriptUsedInCult, Meroitic script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScriptUsedInCult Context triple: [Kushite pantheon, hasScriptUsedInCult, Meroitic script]
-
A.
usesScriptFor
Indicates that one entity employs or relies on a particular script or writing system for its representation, communication, or operation.
-
B.
hasScriptBy
Indicates that one entity has its script authored, written, or created by another entity.
-
C.
hasScriptInfluenceOn
Indicates that one script or writing system has influenced the development, form, or usage of another script.
-
D.
hasCultFeature
chosen
Indicates that an entity possesses a characteristic, attribute, or element associated with cultic or ritual practices.
-
E.
usedInScripts
Indicates that something (such as a tool, method, or resource) is employed or referenced within one or more scripts.
- 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_69f3493c7f6881908edf2aa13631d1e0 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 1, 2026, 1:14 a.m.