Triple
T9889011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mandarin Chinese |
E181408
|
entity |
| Predicate | primaryScriptInTaiwan |
P6524
|
FINISHED |
| Object | Traditional 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: Traditional Chinese characters | Statement: [Mandarin Chinese, primaryScriptInTaiwan, Traditional Chinese characters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryScriptInTaiwan Context triple: [Mandarin Chinese, primaryScriptInTaiwan, Traditional Chinese characters]
-
A.
primaryScript
chosen
Indicates the writing system or script that is chiefly used to represent the language or content of an entity.
-
B.
scriptNameZh
Indicates the Chinese-language name or title of a script.
-
C.
languageOfScriptPromoted
Indicates that a particular language is associated with and promoted through the use of a given writing script.
-
D.
previousPrimaryScriptingLanguage
Indicates that an entity was formerly the main or primary scripting language used by another entity before being replaced or superseded.
-
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_69ca8283a6708190801af7a25a7ebb9f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb47be2988190811a99dc56ae542a |
completed | April 2, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69cd1d810ed48190a252b70e9390c8f3 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:39 p.m.