Triple
T37104563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shapiro delay |
E918804
|
entity |
| Predicate | hasBeenMeasuredNear |
P119237
|
FINISHED |
| Object | the Sun |
—
|
NE NERFINISHED |
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: the Sun | Statement: [Shapiro delay, hasBeenMeasuredNear, the Sun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeenMeasuredNear Context triple: [Shapiro delay, hasBeenMeasuredNear, the Sun]
-
A.
hasMeasurement
Indicates that an entity is associated with a specific measured value, often including a unit or measurement context.
-
B.
wasPreviouslyMeasuredAs
Indicates that an entity had a specific measurement or value at an earlier time, which may differ from its current measurement.
-
C.
isObservedNear
chosen
Indicates that one entity is detected or noticed in close spatial proximity to another entity.
-
D.
isCloseTo
Indicates that one entity is physically or conceptually near another, within a relatively short distance or range.
-
E.
hasFormerUseNearby
Indicates that something in the vicinity previously had a particular use or function that is no longer current.
- 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_69f76e9b99c8819096164b21ff5bd996 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
Created at: May 3, 2026, 4:14 p.m.