Triple
T358289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Convention for the Prevention of Pollution from Ships |
E7592
|
entity |
| Predicate | annex |
P12294
|
FINISHED |
| Object | Annex I |
—
|
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: Annex I | Statement: [International Convention for the Prevention of Pollution from Ships, annex, Annex I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: annex Context triple: [International Convention for the Prevention of Pollution from Ships, annex, Annex I]
-
A.
annexedBy
Indicates that one entity has been incorporated into and brought under the control or sovereignty of another entity.
-
B.
annexCount
Indicates the number of annexes or supplementary parts associated with a primary entity or document.
-
C.
ally
Indicates a cooperative relationship in which one entity supports, assists, or aligns with another, often for mutual benefit or a shared goal.
-
D.
after
Indicates that one event, state, or action occurs later in time than another, following it in temporal order.
-
E.
annexedInYear
Indicates that one entity was formally annexed or incorporated into another in the specified calendar year.
- 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_69a2e7e696948190bebc966535995e45 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebb0e348819086e3ccd96c7b129e |
completed | Feb. 28, 2026, 1:20 p.m. |
| PD | Predicate disambiguation | batch_69a2e959ce948190a201c017eecb7c95 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea2c44408190946267525c88e811 |
completed | Feb. 28, 2026, 1:14 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.