Triple
T334073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DARPA Robotics Challenge |
E6684
|
entity |
| Predicate | thirdPlacePrize |
P12517
|
FINISHED |
| Object | 500000 USD |
—
|
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: 500000 USD | Statement: [DARPA Robotics Challenge, thirdPlacePrize, 500000 USD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdPlacePrize Context triple: [DARPA Robotics Challenge, thirdPlacePrize, 500000 USD]
-
A.
thirdPlacePlayoff
Indicates a match or contest held to determine which participant finishes in third place, typically between the losers of the semifinals.
-
B.
prizeType
Indicates the specific category or kind of prize associated with an entity or event.
-
C.
trophy
Indicates that one entity is a trophy awarded or possessed in relation to another entity, typically as a result of winning or achieving something.
-
D.
thirdParty
Indicates that an entity is a separate, external party involved in a relationship or transaction between two primary entities.
-
E.
awardFor
Indicates that something is given or granted as recognition or a prize for a particular achievement, work, or contribution.
- 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_69a2e79434908190a9d5afe415153ad9 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eac641708190b85fa21368e5de8e |
completed | Feb. 28, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69a2e94d99cc8190a112e4b630ec63c1 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea7d03a88190aab72e61d8673488 |
completed | Feb. 28, 2026, 1:15 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.