Triple
T36106739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ANC |
E1044379
|
entity |
| Predicate | codeStandardPart |
P7659
|
FINISHED |
| Object | ISO 3166-2:PE |
—
|
NE NERFINISHED |
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: ISO 3166-2:PE | Statement: [ANC, codeStandardPart, ISO 3166-2:PE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codeStandardPart Context triple: [ANC, codeStandardPart, ISO 3166-2:PE]
-
A.
codeStandard
Indicates that an entity adheres to, complies with, or is governed by a specified coding or programming standard.
-
B.
codeStandardization
Indicates that multiple pieces of code are being aligned to a common format, style, or set of conventions to ensure consistency.
-
C.
componentStandardization
Indicates that one entity is standardized, normalized, or made uniform according to the specifications, rules, or format defined by another entity.
-
D.
isPartOfStandard
chosen
Indicates that something belongs to, is included within, or conforms to a defined standard or standardized set.
-
E.
documentationStandard
Indicates that there is a specified convention or set of rules governing how documentation should be written, structured, or maintained in relation to an entity or process.
- 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_69f76e338e2c8190b7f3bc68bec76349 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b3e2f3c08190be4fd1ae4fa1266d |
completed | May 3, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bcc47081909fe7d592ac69006c |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.