Triple
T19886509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 5253 |
E477912
|
entity |
| Predicate | gasKinematics |
P91252
|
FINISHED |
| Object | disturbed gas motions |
—
|
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: disturbed gas motions | Statement: [NGC 5253, gasKinematics, disturbed gas motions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gasKinematics Context triple: [NGC 5253, gasKinematics, disturbed gas motions]
-
A.
gasContent
Indicates that one entity has, contains, or is characterized by a certain amount or type of gas.
-
B.
gasSystem
Indicates a relationship where an entity functions as, is part of, or is associated with a gas-based system used for distribution, control, or processing of gases.
-
C.
gasCellsMaterial
Indicates that the material specified is the substance contained within the gas cells.
-
D.
kinematicsIndicate
Indicates that motion-related properties or measurements provide evidence or information about a particular state, condition, or outcome.
-
E.
hasKinematicRegime
chosen
Indicates that an entity is associated with, or operates within, a particular kinematic regime or motion behavior.
- 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_69d8e51f32b08190b3687f4f60353250 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65909fe0481908e22b60d04fe2b11 |
completed | April 20, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69e537e8c4e481909fe95d795b4864e7 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:52 p.m.