Triple
T10054642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Notice |
E208829
|
entity |
| Predicate | circulatedVia |
P91849
|
FINISHED |
| Object | INTERPOL secure communication channels |
—
|
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: INTERPOL secure communication channels | Statement: [Green Notice, circulatedVia, INTERPOL secure communication channels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: circulatedVia Context triple: [Green Notice, circulatedVia, INTERPOL secure communication channels]
-
A.
circulatedAs
Indicates that something was distributed, shared, or passed around in the form or role specified by the related entity.
-
B.
circulatedFrom
Indicates that something has moved or been distributed outward starting from a particular source or origin.
-
C.
circulatedDuring
Indicates that something was in active distribution or use throughout a specified time period or event.
-
D.
hadCirculationIn
Indicates that an entity (such as a publication or medium) had its copies distributed or circulated within a specified location or region.
-
E.
circulatesIn
Indicates that something moves or flows repeatedly within a particular space, system, or medium.
- 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_69ca836094408190a36a1ea7e9a86fcd |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcfab39408190ac728fe156eed658 |
completed | April 2, 2026, 2:08 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8d2280819089de27e57babd1f3 |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4f8d9b888190b8067bd916dae773 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 8:57 p.m.