Triple
T1226549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 3166/MA |
E26339
|
entity |
| Predicate | processes |
P924
|
FINISHED |
| Object | requests for new country codes |
—
|
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: requests for new country codes | Statement: [ISO 3166/MA, processes, requests for new country codes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: processes Context triple: [ISO 3166/MA, processes, requests for new country codes]
-
A.
partOfProcess
Indicates that one event, step, or action occurs as a component or stage within a larger overall process.
-
B.
secondaryProcess
Indicates that an action or process occurs as a secondary, supporting, or subordinate operation relative to a primary process.
-
C.
primaryProcess
Indicates that one process is the main or most fundamental process in relation to another process or within a given system or context.
-
D.
usedProcess
chosen
Indicates that an entity employed or applied a particular process to achieve a result or perform an action.
-
E.
mediatesProcess
Indicates that an entity serves as an intermediary or conduit through which a process occurs, is carried out, or is regulated.
- 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_69a49484688c8190a1bf285eb396a8b6 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be39908481908cca21aaf0828415 |
completed | March 1, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69a4bb65d61c8190bf0424ea0019a98b |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.