Triple
T10507980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Amendment |
E247833
|
entity |
| Predicate | tightens |
P94285
|
FINISHED |
| Object | phase-out schedules for ozone-depleting substances |
—
|
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: phase-out schedules for ozone-depleting substances | Statement: [London Amendment, tightens, phase-out schedules for ozone-depleting substances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tightens Context triple: [London Amendment, tightens, phase-out schedules for ozone-depleting substances]
-
A.
isTight
Indicates that one entity fits closely or securely around, against, or within another without looseness or extra space.
-
B.
tension
Indicates a state of strain, stress, or conflict existing between entities, often involving opposing forces, interests, or emotions.
-
C.
hasTension
Indicates the presence of strain, stress, or conflict between entities in their relationship or interaction.
-
D.
strengthens
Indicates that one entity increases the power, effectiveness, or resilience of another.
-
E.
rinkType
Indicates the specific kind or category of rink associated with an entity (e.g., ice rink, roller rink, practice rink).
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509b287ac8190805a2375bd16b7ae |
completed | April 7, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69d4fb919ea08190bcc1193e2014d437 |
completed | April 7, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69d4fe058fcc81909428137d9ffd6d90 |
completed | April 7, 2026, 12:52 p.m. |
Created at: April 6, 2026, 12:26 p.m.