Triple
T3161935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beijing Municipal Administration and Communication Card |
E66120
|
entity |
| Predicate | scriptOnCard |
P9329
|
FINISHED |
| Object | Simplified Chinese |
—
|
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: Simplified Chinese | Statement: [Beijing Municipal Administration and Communication Card, scriptOnCard, Simplified Chinese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptOnCard Context triple: [Beijing Municipal Administration and Communication Card, scriptOnCard, Simplified Chinese]
-
A.
scriptOnFlag
Indicates that a script is attached to and/or executed when a specific flag or condition is set.
-
B.
scriptOnRibbon
Indicates that a piece of writing or inscription is present on a ribbon associated with the subject.
-
C.
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.
-
D.
scriptCode
chosen
Indicates that an entity is associated with a particular writing system or script, identified by a standardized script code.
-
E.
scriptName
Indicates the name or title of a script associated with an entity, typically identifying which script is used, referenced, or executed in a given context.
- 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_69ad85850c1481908a9e9c6242238de2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada618b9b88190afaa6d47dcad9f2c |
completed | March 8, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfe0a948190928f2201d671c654 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:06 p.m.