Triple
T15830084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SEXTANT |
E383845
|
entity |
| Predicate | usesReferenceObjects |
P119804
|
FINISHED |
| Object | rotation-powered pulsars |
—
|
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: rotation-powered pulsars | Statement: [SEXTANT, usesReferenceObjects, rotation-powered pulsars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesReferenceObjects Context triple: [SEXTANT, usesReferenceObjects, rotation-powered pulsars]
-
A.
usesFoundObject
Indicates that an entity makes use of an object that it has previously found or discovered.
-
B.
requiresReferent
Indicates that one entity depends on or must reference another specific entity in order to be valid, interpretable, or complete.
-
C.
isReferencedIn
Indicates that one entity is cited, mentioned, or otherwise referred to within another entity.
-
D.
hasReferences
Indicates that one entity cites, points to, or relies on another entity as a reference or source.
-
E.
usedReferenceFrame
Indicates that one entity adopts or relies on another entity as the coordinate system or reference frame for describing positions, motions, or measurements.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e11e636bb48190a6b39feb550aaa3d |
completed | April 16, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69e007647f908190adb178c68c7bb7cf |
completed | April 15, 2026, 9:47 p.m. |
Created at: April 10, 2026, 4:49 a.m.