Triple
T1625225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CST (China Standard Time) |
E35124
|
entity |
| Predicate | standardAbbreviationContext |
P12874
|
FINISHED |
| Object | timekeeping in China |
—
|
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: timekeeping in China | Statement: [CST (China Standard Time), standardAbbreviationContext, timekeeping in China]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardAbbreviationContext Context triple: [CST (China Standard Time), standardAbbreviationContext, timekeeping in China]
-
A.
establishesAbbreviation
chosen
Indicates that one entity defines or introduces an abbreviated form that stands for another entity.
-
B.
standardPrefix
Indicates that one entity serves as the conventional or officially recognized prefix used before another entity.
-
C.
notAbbreviationOf
Indicates that one term is explicitly asserted not to be an abbreviation or shortened form of another term.
-
D.
standardFormUsedIn
Indicates that a particular standard form is employed or applied within a given context, process, or system.
-
E.
standardType
Indicates that one entity is classified as the standard, canonical, or reference type for another entity or 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_69a886023194819080a3fccd6e325d0e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9431af5ac8190893133f1ae490142 |
completed | March 5, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69a907c91c888190b6ed295c1a2e0977 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.