Triple
T3013553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agreement on Preshipment Inspection |
E82278
|
entity |
| Predicate | requires |
P100
|
FINISHED |
| Object | notification of exporters about inspection findings within a reasonable time |
—
|
LITERAL FINISHED |
How this triple was built (1 step)
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: notification of exporters about inspection findings within a reasonable time | Statement: [Agreement on Preshipment Inspection, requires, notification of exporters about inspection findings within a reasonable time]
Provenance (2 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_69ad8b1eb53481908c39bbcd1ec104b2 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a6883c081909b6b74f078e347b7 |
completed | March 8, 2026, 3:48 p.m. |
Created at: March 8, 2026, 3 p.m.