Triple
T10162375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Scientific Basis |
E233920
|
entity |
| Predicate | usedInforms |
P92359
|
FINISHED |
| Object | international climate policy discussions |
—
|
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: international climate policy discussions | Statement: [The Scientific Basis, usedInforms, international climate policy discussions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInforms Context triple: [The Scientific Basis, usedInforms, international climate policy discussions]
-
A.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
B.
usedOn
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to another entity.
-
C.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
D.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
-
E.
usedDuring
Indicates that one entity is employed, applied, or active in the course of another entity’s process, event, or time period.
- 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_69ca848e80748190b91d1e04d35512c7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec5b5194819095645e9174897b0f |
completed | April 2, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba795808190acc9124c98c6e40f |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4f8f869c8190a82ad040993e0244 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 9:09 p.m.