Triple
T19831895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galactic OB associations |
E476479
|
entity |
| Predicate | dynamicalEvolution |
P126659
|
FINISHED |
| Object | disperse into the Galactic field |
—
|
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: disperse into the Galactic field | Statement: [Galactic OB associations, dynamicalEvolution, disperse into the Galactic field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynamicalEvolution Context triple: [Galactic OB associations, dynamicalEvolution, disperse into the Galactic field]
-
A.
evolutionaryPhase
Indicates the stage or period an entity is in within a broader process of gradual development or evolution.
-
B.
typicalDynamics
chosen
Indicates the usual or characteristic way in which a system, process, or interaction evolves or behaves over time.
-
C.
futureEvolution
Indicates a predicted or potential future development or transformation of one entity into another.
-
D.
evolves
Indicates that one entity undergoes a process of gradual change or development into another, typically more advanced or different, state or form.
-
E.
dustDynamics
Indicates how dust particles move, interact, and evolve over time within a physical or astrophysical environment.
- 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_69d8e51c7c188190b926f3a2a7b5f881 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e656ce68b48190aa25b29d0b6ea021 |
completed | April 20, 2026, 4:39 p.m. |
| PD | Predicate disambiguation | batch_69e5305bda388190a23b7191768107b1 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:50 p.m.