Triple
T18619481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | COP15 |
E455110
|
entity |
| Predicate | hailedBy |
P74359
|
FINISHED |
| Object | some governments as a step forward |
—
|
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: some governments as a step forward | Statement: [COP15, hailedBy, some governments as a step forward]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hailedBy Context triple: [COP15, hailedBy, some governments as a step forward]
-
A.
honoredThrough
Indicates that one entity is recognized or commemorated by means of another entity, event, or action.
-
B.
championedBy
Indicates that an entity is actively supported, promoted, or advocated for by another entity.
-
C.
celebratedAs
chosen
Indicates that one entity is regarded, honored, or widely recognized as having a particular role, status, or distinction.
-
D.
honoredOn
Indicates that an entity is formally recognized, celebrated, or commemorated on a specific date or occasion.
-
E.
namedInHonorBy
Indicates that one entity has been used as the namesake or dedicatee by another entity, signifying that the latter is named in honor of the former.
- 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_69d8d38bbe7c8190bdec3138e7d413c9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54d07dc288190bb3b8b5ab06518da |
completed | April 19, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69e478d4a7948190a4bb9223bb5dddfc |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:46 a.m.