Triple
T11316904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PSR B1913+16 |
E267990
|
entity |
| Predicate | pulsarSpinPeriod |
P98462
|
FINISHED |
| Object | about 59 milliseconds |
—
|
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: about 59 milliseconds | Statement: [PSR B1913+16, pulsarSpinPeriod, about 59 milliseconds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pulsarSpinPeriod Context triple: [PSR B1913+16, pulsarSpinPeriod, about 59 milliseconds]
-
A.
radialVelocitySignalPeriodicity
Indicates that the radial velocity measurements of an object exhibit a repeating, periodic signal over time.
-
B.
hasOrbitalPeriod
Indicates that one entity completes a full orbit around another entity within a specified duration.
-
C.
nodePrecessionPeriod
Indicates the duration of time it takes for the line of nodes of an orbit to complete one full precessional cycle relative to a reference frame.
-
D.
hasRotationalVelocityKmPerSec
Indicates that an entity possesses a rotational speed measured in kilometers per second.
-
E.
pendulumPeriod
Indicates the duration of time it takes for a pendulum to complete one full back-and-forth swing.
- 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9c3cf748190987838029d9f7fff |
completed | April 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69d787ad575081908274280bf75d95fd |
completed | April 9, 2026, 11:04 a.m. |
| PDg | Predicate description generation | batch_69d796d049e88190a9fd7508f477f541 |
completed | April 9, 2026, 12:08 p.m. |
Created at: April 8, 2026, 9:32 p.m.