Triple
T26096530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cia-Cia |
E658283
|
entity |
| Predicate | scriptAdoptionAttempt |
P162135
|
FINISHED |
| Object | Hangul |
—
|
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: Hangul | Statement: [Cia-Cia, scriptAdoptionAttempt, Hangul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptAdoptionAttempt Context triple: [Cia-Cia, scriptAdoptionAttempt, Hangul]
-
A.
scriptAdaptationFrom
Indicates that a script is adapted or derived from a pre-existing source work (such as a book, play, or earlier script).
-
B.
scriptOnFlag
Indicates that a script is attached to and/or executed when a specific flag or condition is set.
-
C.
scriptPromoted
Indicates that a script has been elevated in status or visibility, such as being featured, recommended, or moved to a higher-priority category.
-
D.
scriptUsageChange
Indicates a change in how a script is used, such as modifications to its invocation, parameters, frequency, or execution context over time.
-
E.
script
Indicates that an entity is associated with a written text or code (such as a screenplay, program, or written instructions) that defines its content or behavior.
- 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_69ee5bbfc4d08190a1b206d0ac3a1e8d |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f622abdfac8190988421c946411d7e |
completed | May 2, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621fbfc2c8190bfa802d7dc0f6aa4 |
completed | May 2, 2026, 4:10 p.m. |
Created at: April 26, 2026, 7:51 p.m.