Triple
T21326909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 4459 |
E525781
|
entity |
| Predicate | hasKinematicsStudy |
P143729
|
FINISHED |
| Object | stellar kinematics |
—
|
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: stellar kinematics | Statement: [NGC 4459, hasKinematicsStudy, stellar kinematics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKinematicsStudy Context triple: [NGC 4459, hasKinematicsStudy, stellar kinematics]
-
A.
hasKinetics
Indicates that one entity is associated with the kinetic properties or rate-related behavior of another entity in a process or reaction.
-
B.
hasKinematicRegime
Indicates that an entity is associated with, or operates within, a particular kinematic regime or motion behavior.
-
C.
hasKinematicUse
Indicates that one entity is used in a kinematic context or role within the motion or movement behavior of another entity.
-
D.
hasKinematicProperty
Indicates that an entity possesses a specific motion-related characteristic, such as velocity, acceleration, or trajectory.
-
E.
hasKinematicRole
Indicates that an entity participates in a motion or physical interaction with a specific kinematic function or role (e.g., mover, pivot, link) within a dynamic system.
- 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_69e0b51b90788190a4dd823d962626da |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7ab4a796081908148ec9106362d3d |
completed | April 21, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
| PDg | Predicate description generation | batch_69e6190163448190a2404b396215c686 |
completed | April 20, 2026, 12:16 p.m. |
Created at: April 16, 2026, 4:41 p.m.