Triple
T8031983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gan |
E187005
|
entity |
| Predicate | hasISOCodeContext |
P32679
|
FINISHED |
| Object | Chinese provincial abbreviations |
—
|
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 provincial abbreviations | Statement: [Gan, hasISOCodeContext, Chinese provincial abbreviations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasISOCodeContext Context triple: [Gan, hasISOCodeContext, Chinese provincial abbreviations]
-
A.
hasISOCode
Indicates that an entity is associated with a specific standardized ISO code that uniquely identifies it according to ISO conventions.
-
B.
hasISOCodeType
Indicates that an entity is associated with a specific type or category of ISO code (e.g., country code, currency code, language code).
-
C.
hasISOClassificationContext
Indicates that an entity is associated with a specific ISO-based classification context under which its classification or categorization is defined.
-
D.
ISOCodeContext
chosen
Indicates the contextual framework or domain within which a particular ISO code is defined, interpreted, or applied.
-
E.
isCurrentISOCode
Indicates that an entity’s code is the officially recognized, up-to-date ISO standard code for that entity.
- 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_69ca82ae2d1081909dbfee42b41db419 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3ef18da48190835454a5eb969da7 |
completed | March 31, 2026, 3:26 a.m. |
| PD | Predicate disambiguation | batch_69cb049688208190b32088bd2c5930bc |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:22 p.m.