Triple
T868860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Local Interstellar Cloud |
E18765
|
entity |
| Predicate | hasKinematicProperty |
P20339
|
FINISHED |
| Object | flows past the Sun |
—
|
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: flows past the Sun | Statement: [Local Interstellar Cloud, hasKinematicProperty, flows past the Sun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKinematicProperty Context triple: [Local Interstellar Cloud, hasKinematicProperty, flows past the Sun]
-
A.
hasCenterOfMassMomentum
Indicates that one entity possesses or is characterized by a specific value of momentum associated with its center of mass.
-
B.
hasRelativeAngularMomentum
Indicates that one entity possesses angular momentum defined relative to another reference entity or frame.
-
C.
hasKPoint
Indicates that an entity possesses or is associated with a specific K-point, typically a designated point in reciprocal or parameter space.
-
D.
hasMomentumState
Indicates that an entity possesses a particular state or condition related to its momentum (e.g., magnitude, direction, or dynamic status).
-
E.
usesMovement
Indicates that an entity performs or involves some form of movement as part of its action or behavior.
- 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_69a4938ce8688190a24bdfef82ba7d21 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac7f98908190883f71049092c7c8 |
completed | March 1, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69a4aa87504481909618a6815948da6f |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab498bb0819080e3afb684b504b6 |
completed | March 1, 2026, 9:10 p.m. |
Created at: March 1, 2026, 7:39 p.m.