Triple
T26226711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Authorized Economic Operator (AEO) programme in India |
E655909
|
entity |
| Predicate | revisedGuidelinesIssued |
P160376
|
FINISHED |
| Object | 2016 |
—
|
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: 2016 | Statement: [Authorized Economic Operator (AEO) programme in India, revisedGuidelinesIssued, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revisedGuidelinesIssued Context triple: [Authorized Economic Operator (AEO) programme in India, revisedGuidelinesIssued, 2016]
-
A.
dateRevisedTo
Indicates that an entity’s date has been updated or changed to a new specified date.
-
B.
hasGuideline
Indicates that one entity is governed, informed, or constrained by a rule, standard, or recommended procedure provided by another entity.
-
C.
revisedByStandard
Indicates that something has been updated or modified in accordance with a specified standard or set of standards.
-
D.
notableGuideline
Indicates that something is recognized as an important or especially significant rule, principle, or recommended practice.
-
E.
guidelineNumber
Indicates the specific numeric identifier assigned to a guideline within a set of rules, standards, or recommendations.
- 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_69ee5b4a77e08190bfcb5f8ecdc55abd |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60d53d94081909d0ae8f05e8de84c |
completed | May 2, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f600be0de88190989611e952b03117 |
completed | May 2, 2026, 1:48 p.m. |
Created at: April 26, 2026, 8:58 p.m.