Triple
T7558750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CC |
E178739
|
entity |
| Predicate | associatedSubdivisionCodePrefix |
P54482
|
FINISHED |
| Object | CC |
—
|
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: CC | Statement: [CC, associatedSubdivisionCodePrefix, CC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedSubdivisionCodePrefix Context triple: [CC, associatedSubdivisionCodePrefix, CC]
-
A.
associatedCountrySubdivisionCode
Indicates the specific administrative region or subdivision code within a country that is linked to or relevant for the given entity.
-
B.
associatedWithSubdivision
Indicates that one entity has a connection or linkage to a specific administrative or organizational subdivision.
-
C.
hasSubdivisionCode
Indicates that an entity is associated with a specific code identifying one of its internal subdivisions (such as a state, province, or region).
-
D.
hasSubdivisionCodePart
chosen
Indicates that an entity’s subdivision code includes or is composed of the referenced code segment or component.
-
E.
primarySubdivisionOf
Indicates that one administrative or territorial unit is the main first-level subdivision within a larger political or geographic 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_69c69f2da22c8190a50942ac20af70e8 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8dc7d288190a0d08ba704cc3fc2 |
completed | March 27, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69c6f4dc485c819080da13e3b7f4f08f |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:50 p.m.