Triple
T334065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DARPA Robotics Challenge |
E6684
|
entity |
| Predicate | virtualChallengeDate |
P12514
|
FINISHED |
| Object | 2013-06 |
—
|
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: 2013-06 | Statement: [DARPA Robotics Challenge, virtualChallengeDate, 2013-06]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: virtualChallengeDate Context triple: [DARPA Robotics Challenge, virtualChallengeDate, 2013-06]
-
A.
hasChallenge
Indicates that an entity faces, experiences, or is confronted with a particular difficulty, obstacle, or problem.
-
B.
attackDate
Indicates the calendar date on which an attack or assault event took place.
-
C.
demonstrationDate
Indicates the date on which a demonstration or protest event takes place or is scheduled to occur.
-
D.
proposalDate
Indicates the date on which a proposal is formally made or submitted from one entity to another.
-
E.
drinkingWaterChallenge
Indicates a situation where an entity participates in a task or contest that involves consuming a specified amount of water under particular rules or conditions.
- 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.