Triple
T7344995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cia-Cia language |
E169353
|
entity |
| Predicate | writingSystemAttempt |
P26603
|
FINISHED |
| Object | Hangul |
—
|
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: Hangul | Statement: [Cia-Cia language, writingSystemAttempt, Hangul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writingSystemAttempt Context triple: [Cia-Cia language, writingSystemAttempt, Hangul]
-
A.
writingSystem
Indicates that one entity is the script or system of written symbols used to represent the language or content of another entity.
-
B.
writingSystemUsedIn
chosen
Indicates that a particular writing system is employed for written communication within a given language, region, or context.
-
C.
writingSystemFound
Indicates that a particular writing system is present, attested, or used in association with a given entity (such as a language, region, or community).
-
D.
writingSystemStage
Indicates the developmental or historical stage a particular writing system is in or associated with.
-
E.
writingSystemLacks
Indicates that a particular writing system does not possess, include, or support a specified feature, element, or capability.
- 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_69c68a57710481909f0c1f3c6ebdb6f2 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f139505c8190a7158cf59a6e089e |
completed | March 27, 2026, 9:06 p.m. |
| PD | Predicate disambiguation | batch_69c6f02aeeb8819099d1626566cec18b |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:05 p.m.