Triple
T30979513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revive Our Oceans |
E789324
|
entity |
| Predicate | prizeWinnersReceive |
P14849
|
FINISHED |
| Object | funding for implementation and scaling |
—
|
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: funding for implementation and scaling | Statement: [Revive Our Oceans, prizeWinnersReceive, funding for implementation and scaling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prizeWinnersReceive Context triple: [Revive Our Oceans, prizeWinnersReceive, funding for implementation and scaling]
-
A.
winnerReceives
chosen
Indicates that the entity identified as the winner is granted or awarded the specified item, benefit, or outcome as a result of winning.
-
B.
awardeesReceive
Indicates that designated awardees are the recipients of a particular award or honor.
-
C.
isPrizedFor
Indicates that something is highly valued or esteemed because of a particular quality, feature, or benefit it provides.
-
D.
prizeTakenTo
Indicates that a prize is physically transported or carried from one location to another.
-
E.
prizeContext
Indicates the situational or contextual circumstances under which a prize is awarded, considered, or relevant.
- 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_69f224c4831c8190be53924ec25a150a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:55 p.m.