Triple
T5201980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SagDEG |
E117412
|
entity |
| Predicate | hasKinematicFeature |
P20339
|
FINISHED |
| Object | stars follow coherent tidal streams |
—
|
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: stars follow coherent tidal streams | Statement: [SagDEG, hasKinematicFeature, stars follow coherent tidal streams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKinematicFeature Context triple: [SagDEG, hasKinematicFeature, stars follow coherent tidal streams]
-
A.
hasKinematicProperty
chosen
Indicates that an entity possesses a specific motion-related characteristic, such as velocity, acceleration, or trajectory.
-
B.
hasKinematicCenterApprox
Indicates that an entity has an approximate kinematic center location or value associated with it.
-
C.
hasMountingFeature
Indicates that one entity includes or provides a structural feature intended for mounting or attaching another entity.
-
D.
hasFeatureCode
Indicates that an entity is associated with a specific feature identifier or code that characterizes one of its properties or attributes.
-
E.
hasMovementType
Indicates the type or mode of movement associated with an entity, such as how it moves or is transported.
- 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_69bd4463dd3c81909966123f20b79d57 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7adb034c819086bf8a85fbf158f4 |
completed | March 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69bd77b9a67c8190819612257ea746b4 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:47 p.m.