Triple
T11316980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PSR B1937+21 |
E267991
|
entity |
| Predicate | pulsePeriodStability |
P98472
|
FINISHED |
| Object | extremely high |
—
|
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: extremely high | Statement: [PSR B1937+21, pulsePeriodStability, extremely high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pulsePeriodStability Context triple: [PSR B1937+21, pulsePeriodStability, extremely high]
-
A.
pulseDuration
Indicates the length of time that a pulse or discrete signal remains active or at a specified level.
-
B.
peakServicePeriod
Indicates the time interval during which a service experiences its highest or most intensive level of use or operation.
-
C.
radialVelocitySignalPeriodicity
Indicates that the radial velocity measurements of an object exhibit a repeating, periodic signal over time.
-
D.
beatCharacteristic
Indicates a characteristic or quality that defines or describes a particular beat (such as its style, pattern, or rhythmic property).
-
E.
rotationPeriod_hours
Indicates the length of time, measured in hours, that an object takes to complete one full rotation on its axis.
- 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.