Triple
T292907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNESCO Gold Medal Award |
E6031
|
entity |
| Predicate | aimsToPromote |
P1258
|
FINISHED |
| Object | scientific advancement |
—
|
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: scientific advancement | Statement: [UNESCO Gold Medal Award, aimsToPromote, scientific advancement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimsToPromote Context triple: [UNESCO Gold Medal Award, aimsToPromote, scientific advancement]
-
A.
aimsToProvide
Indicates that one entity intends or is designed to supply, deliver, or make available something to another entity.
-
B.
promotes
chosen
Indicates that one entity actively supports, advances, or encourages the growth, adoption, or success of another entity or outcome.
-
C.
aimsToProtect
Indicates an intention or purpose to safeguard or defend one entity, value, or condition from harm, risk, or undesirable outcomes.
-
D.
aimsToBalance
Indicates an intention or effort by one entity to bring multiple elements, forces, or conditions into a state of equilibrium.
-
E.
aimsToExplain
Indicates that one entity intends to clarify, make understandable, or provide an explanation about another entity, concept, or situation.
- 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_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea0dd1dc8190aecd5afdeb2fd74b |
completed | Feb. 28, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69a2e934b4408190b53a17f57a02df65 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.