Triple
T156151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 3166-1 numeric |
E3185
|
entity |
| Predicate | belongsToDomain |
P1248
|
FINISHED |
| Object | geopolitical coding |
—
|
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: geopolitical coding | Statement: [ISO 3166-1 numeric, belongsToDomain, geopolitical coding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToDomain Context triple: [ISO 3166-1 numeric, belongsToDomain, geopolitical coding]
-
A.
usedInDomain
chosen
Indicates that something (such as a concept, method, or resource) is applied or utilized within a particular domain or field.
-
B.
belongsToFamily
Indicates that an entity is a member of, or is associated as part of, a specific family group.
-
C.
regulatoryDomain
Indicates that one entity defines or governs the rules, policies, or constraints under which another entity must operate.
-
D.
ownedBy
Indicates that one entity possesses legal or rightful ownership of another entity.
-
E.
hasAdministrativeUnit
Indicates that one entity possesses, contains, or is associated with another entity that functions as its administrative subdivision or governing unit.
- 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a258808ff08190a06b6206f635612b |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a2565ded588190a27319aaa0130b4f |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.