Triple
T10508117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beijing Amendment |
E247836
|
entity |
| Predicate | tightensControlOn |
P69335
|
FINISHED |
| Object | hydrochlorofluorocarbons |
—
|
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: hydrochlorofluorocarbons | Statement: [Beijing Amendment, tightensControlOn, hydrochlorofluorocarbons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tightensControlOn Context triple: [Beijing Amendment, tightensControlOn, hydrochlorofluorocarbons]
-
A.
aimsToControl
chosen
Indicates an intention or effort by one entity to gain power over, direct, or regulate another entity or situation.
-
B.
rangeControlledBy
Indicates that the extent or scope of something is regulated, limited, or determined by another entity.
-
C.
exportControl
Indicates that an entity is subject to rules or restrictions governing the transfer or export of goods, services, or information across borders.
-
D.
effectControlledBy
Indicates that the occurrence, magnitude, or outcome of one effect is regulated, determined, or constrained by another specified factor or agent.
-
E.
affectedControlOf
Indicates that one entity has influenced, altered, or impacted the degree of control another entity has over something.
- F. None of above.
Provenance (3 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. |
Created at: April 6, 2026, 12:26 p.m.