Triple
T11316963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PSR B1937+21 |
E267991
|
entity |
| Predicate | hasPulseProfile |
P9523
|
FINISHED |
| Object | main pulse and interpulse |
—
|
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: main pulse and interpulse | Statement: [PSR B1937+21, hasPulseProfile, main pulse and interpulse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPulseProfile Context triple: [PSR B1937+21, hasPulseProfile, main pulse and interpulse]
-
A.
hasProfile
chosen
Indicates that an entity is associated with or possesses a specific profile representation or account.
-
B.
beatCharacteristic
Indicates a characteristic or quality that defines or describes a particular beat (such as its style, pattern, or rhythmic property).
-
C.
hasBPMApprox
Indicates an approximate beats-per-minute (BPM) value associated with an entity, rather than an exact measured tempo.
-
D.
hasBeat
Indicates that one entity has defeated or surpassed another in a competitive or comparative context.
-
E.
hasPeakAssociated
Indicates that one entity is linked or related to a specific peak (such as a summit or maximum point) associated with it.
- 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_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. |
Created at: April 8, 2026, 9:32 p.m.