Triple
T37104543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shapiro delay |
E918804
|
entity |
| Predicate | firstTestContext |
P205727
|
FINISHED |
| Object | radar ranging to Venus and Mercury |
—
|
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: radar ranging to Venus and Mercury | Statement: [Shapiro delay, firstTestContext, radar ranging to Venus and Mercury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstTestContext Context triple: [Shapiro delay, firstTestContext, radar ranging to Venus and Mercury]
-
A.
firstTest
Indicates that an entity is the initial or earliest test in a sequence or set of tests.
-
B.
firstTestLaunch
Indicates that an entity’s initial test launch event occurs, marking the first time it is experimentally deployed or sent into operation.
-
C.
centralTest
Indicates that an entity serves as the primary or core test within a set of tests or an evaluation process.
-
D.
firstTestYear
Indicates the year in which an entity’s first test or testing activity took place.
-
E.
firstTestVenue
Indicates the venue where something (such as an event, performance, or test) was held or conducted for the first time.
- 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_69f76e9b99c8819096164b21ff5bd996 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:14 p.m.