Triple
T26896833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arendellian |
E677918
|
entity |
| Predicate | writingSystemInspiredBy |
P161311
|
FINISHED |
| Object | runic alphabets |
—
|
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: runic alphabets | Statement: [Arendellian, writingSystemInspiredBy, runic alphabets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writingSystemInspiredBy Context triple: [Arendellian, writingSystemInspiredBy, runic alphabets]
-
A.
writingSystemDevelopedFor
Indicates that a particular writing system was created or adapted specifically to be used for a given language, community, or purpose.
-
B.
writingSystem
Indicates that one entity is the script or system of written symbols used to represent the language or content of another entity.
-
C.
writingSystemDevelopedFrom
Indicates that one writing system originated, evolved, or was derived from another earlier writing system.
-
D.
writingSystemUsedIn
Indicates that a particular writing system is employed for written communication within a given language, region, or context.
-
E.
writingSystemDeciphered
Indicates that the writing system used by an entity has been successfully interpreted and its symbols and structure are understood.
- 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_69eee9befee48190a26f214faa867be7 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61faa702c81909489a6d40e8ee023 |
completed | May 2, 2026, 4 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
| PDg | Predicate description generation | batch_69f6125e54e0819088ee33a20efcc9e6 |
completed | May 2, 2026, 3:03 p.m. |
Created at: April 27, 2026, 5:48 a.m.