Triple
T735480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chan |
E14920
|
entity |
| Predicate | writingSystemOfOrigin |
P9874
|
FINISHED |
| Object | Chinese characters |
—
|
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: Chinese characters | Statement: [Chan, writingSystemOfOrigin, Chinese characters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writingSystemOfOrigin Context triple: [Chan, writingSystemOfOrigin, Chinese characters]
-
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.
writingSystemDevelopedFrom
chosen
Indicates that one writing system originated, evolved, or was derived from another earlier writing system.
-
C.
writingSystemClass
Indicates that one entity is classified as a type or category of writing system to which the other entity belongs.
-
D.
writingSystemUsedSince
Indicates that a particular writing system has been in use starting from a specified point in time or period.
-
E.
writingSystemFeatures
Indicates the specific structural or functional characteristics that define how a particular writing system represents language.
- 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_69a4934d9930819099eed80096b0597d |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a66820548190b373deb117187c2c |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a4fafee081909bf356854c09aaff |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.