Triple
T6450062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CA-NL |
E139839
|
entity |
| Predicate | hasSubdivisionTypeCode |
P36805
|
FINISHED |
| Object | province 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: province code | Statement: [CA-NL, hasSubdivisionTypeCode, province code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubdivisionTypeCode Context triple: [CA-NL, hasSubdivisionTypeCode, province code]
-
A.
hasSubdivisionCode
Indicates that an entity is associated with a specific code identifying one of its internal subdivisions (such as a state, province, or region).
-
B.
hasTypeOfSubdivision
chosen
Indicates that one administrative or territorial unit is classified as a specific kind or category of subdivision.
-
C.
hasSubdivisionCodePart
Indicates that an entity’s subdivision code includes or is composed of the referenced code segment or component.
-
D.
hasSubdivision
Indicates that one entity is divided into and contains another entity as one of its constituent parts or administrative units.
-
E.
hasSubdivisionStandard
Indicates that a governing standard or specification defines how an entity is to be subdivided into smaller parts or units.
- 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_69c008b301948190a35854e5284dc822 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c069b2c7bc81908c683ec22cad9628 |
completed | March 22, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69c0673b44148190aed70084f0ff4992 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:47 p.m.