Triple
T126249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 3166-2:PR |
E2556
|
entity |
| Predicate | notationSystem |
P6517
|
FINISHED |
| Object | alphanumeric 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: alphanumeric code | Statement: [ISO 3166-2:PR, notationSystem, alphanumeric code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notationSystem Context triple: [ISO 3166-2:PR, notationSystem, alphanumeric code]
-
A.
notationType
Indicates the specific system or style of notation used to represent or encode something (such as music, math, or language).
-
B.
writingSystem
Indicates that one entity is the script or system of written symbols used to represent the language or content of another entity.
-
C.
notableSystem
Indicates that a system is recognized as significant, prominent, or noteworthy in a particular context or domain.
-
D.
usesNamingSystem
Indicates that one entity adopts or applies a particular naming system or convention to identify or label other entities.
-
E.
definedMonetarySystem
Indicates that an authority or entity has established and specified the rules, structure, and characteristics of a particular monetary system.
- F. None of above. chosen
Provenance (4 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_69a251b54ea88190b18281669f59b4c0 |
completed | Feb. 28, 2026, 2:23 a.m. |
| NER | Named-entity recognition | batch_69a25760af348190bf402089c240887d |
completed | Feb. 28, 2026, 2:48 a.m. |
| PD | Predicate disambiguation | batch_69a2564c11208190ad25495609d94d87 |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2575d8a648190ad8e10d4b04e5e07 |
completed | Feb. 28, 2026, 2:47 a.m. |
Created at: Feb. 28, 2026, 2:27 a.m.