Triple
T7636175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yue |
E172883
|
entity |
| Predicate | isWrittenWithScript |
P454
|
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: [Yue, isWrittenWithScript, Chinese characters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWrittenWithScript Context triple: [Yue, isWrittenWithScript, Chinese characters]
-
A.
writingSystem
chosen
Indicates that one entity is the script or system of written symbols used to represent the language or content of another entity.
-
B.
hasOfficialWritingSystem
Indicates that an entity (typically a language) is associated with a formally recognized and standardized writing system used for official or standard purposes.
-
C.
writingSystemUsedIn
Indicates that a particular writing system is employed for written communication within a given language, region, or context.
-
D.
associatedLanguageScript
Indicates that there is a relationship between a language and the script or writing system used to represent it.
-
E.
nativeNameScript
Indicates the writing system or script in which an entity’s native name is expressed.
- 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_69c69952849881908fdcea7a93bfc307 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6faa95e488190962c23609e0890a5 |
completed | March 27, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e8cadc8190b7977fcd213954dd |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:57 p.m.