Triple
T9554586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhangzhou dialect |
E230508
|
entity |
| Predicate | ISOException |
P66441
|
FINISHED |
| Object | no separate ISO 639-3 code |
—
|
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: no separate ISO 639-3 code | Statement: [Zhangzhou dialect, ISOException, no separate ISO 639-3 code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ISOException Context triple: [Zhangzhou dialect, ISOException, no separate ISO 639-3 code]
-
A.
isoStatus
Indicates the ISO (International Organization for Standardization) compliance or certification status associated with an entity or process.
-
B.
isInternationalStandard
Indicates that something has been formally recognized or adopted as a standard at the international level.
-
C.
isNumberingException
chosen
Indicates that an item deviates from the standard or expected numbering sequence or rules.
-
D.
isoClassificationStatus
Indicates the current status or stage of an entity within an ISO-based classification or standardization process.
-
E.
securityAlliance
Indicates a formal cooperative relationship in which entities agree to support and protect each other’s security interests, often including mutual defense or coordinated security measures.
- 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_69ca847d3be8819099c9dad2a7e786f1 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd992412148190b092bd9918764d5f |
completed | April 1, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69ccd594d0ac8190a81bc11a3a538167 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:03 p.m.