Triple
T29968711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yellow Notice |
E761259
|
entity |
| Predicate | mayBePublishedAs |
P178610
|
FINISHED |
| Object | public extract on INTERPOL website |
—
|
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: public extract on INTERPOL website | Statement: [Yellow Notice, mayBePublishedAs, public extract on INTERPOL website]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBePublishedAs Context triple: [Yellow Notice, mayBePublishedAs, public extract on INTERPOL website]
-
A.
isPublishedWith
Indicates that an entity is released or made publicly available together with another specified entity, typically as part of the same publication or release event.
-
B.
isPublished
Indicates that an item has been formally made available to the public through some publishing process.
-
C.
mayPublish
Indicates that an entity has the permission or authorization to publish another entity or piece of content.
-
D.
publishedAs
Indicates that an entity is released, issued, or made publicly available under a particular name, format, or identity.
-
E.
publishesFor
Indicates that one entity issues, releases, or makes content publicly available on behalf of, or in service of, another entity.
- 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_69f22467626081908d5afea489590e96 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f7117cf2188190b29e36fc1e342c60 |
completed | May 3, 2026, 9:12 a.m. |
Created at: April 29, 2026, 6:31 p.m.