Triple
T22549871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xiaoerjing |
E557529
|
entity |
| Predicate | scriptModification |
P32645
|
FINISHED |
| Object | adds letters for Chinese consonants |
—
|
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: adds letters for Chinese consonants | Statement: [Xiaoerjing, scriptModification, adds letters for Chinese consonants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptModification Context triple: [Xiaoerjing, scriptModification, adds letters for Chinese consonants]
-
A.
scriptCode
Indicates that an entity is associated with a particular writing system or script, identified by a standardized script code.
-
B.
scriptEditor
Indicates that an entity serves as the editor or editing environment used to create or modify a script.
-
C.
scriptChangePolicy
Indicates a policy governing when, how, or under what conditions a script may be modified or updated.
-
D.
scriptEvolution
chosen
Indicates how a script or written system changes, develops, or transforms over time in relation to its earlier or later forms.
-
E.
modificationProgram
Indicates that an entity is subject to, or associated with, a program or process that alters, updates, or changes its properties or state.
- 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_69e11e59db848190b4272ecd2b690ffd |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15f74512c8190b5369e19a4bc6325 |
completed | April 29, 2026, 1:31 a.m. |
| PD | Predicate disambiguation | batch_69e898cb3fb48190add6ab24a2df5822 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:52 p.m.