Triple
T126227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 3166-2:PR |
E2556
|
entity |
| Predicate | standardCategory |
P87
|
FINISHED |
| Object | subdivision code standard |
—
|
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: subdivision code standard | Statement: [ISO 3166-2:PR, standardCategory, subdivision code standard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardCategory Context triple: [ISO 3166-2:PR, standardCategory, subdivision code standard]
-
A.
category
chosen
Indicates that one entity is classified as a member or type within the grouping or class defined by another entity.
-
B.
standardType
Indicates that one entity is classified as the standard, canonical, or reference type for another entity or context.
-
C.
protectedCategory
Indicates that one entity is classified under a legally or formally recognized group that is granted special protection from discrimination or adverse treatment.
-
D.
standardNumber
Indicates that an entity is associated with a canonical or officially recognized reference number used for identification or classification.
-
E.
classificationStart
Indicates the point in time or process at which a classification or categorization of an entity begins.
- 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_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. |
Created at: Feb. 28, 2026, 2:27 a.m.