Triple
T37104565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shapiro delay |
E918804
|
entity |
| Predicate | hasBeenMeasuredIn |
P24236
|
FINISHED |
| Object | binary pulsar PSR B1913+16 |
—
|
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: binary pulsar PSR B1913+16 | Statement: [Shapiro delay, hasBeenMeasuredIn, binary pulsar PSR B1913+16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeenMeasuredIn Context triple: [Shapiro delay, hasBeenMeasuredIn, binary pulsar PSR B1913+16]
-
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.
hasMeasuredParameter
Indicates that an entity has a specific parameter that has been quantitatively measured or recorded.
-
D.
containsMeasure
Indicates that one entity includes or encompasses a specific measure or quantitative component as part of its content or structure.
-
E.
measuredBy
chosen
Indicates that something’s quantity, extent, or value is determined or expressed using a particular measurement method, instrument, or unit.
- 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_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: May 3, 2026, 4:14 p.m.