Triple
T20777912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hydra–Centaurus |
E511400
|
entity |
| Predicate | roleInCosmicFlow |
P59362
|
FINISHED |
| Object | major attractor in local velocity 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: major attractor in local velocity field | Statement: [Hydra–Centaurus, roleInCosmicFlow, major attractor in local velocity field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInCosmicFlow Context triple: [Hydra–Centaurus, roleInCosmicFlow, major attractor in local velocity field]
-
A.
roleInCosmos
chosen
Indicates the function, position, or significance an entity holds within the larger structure or order of the cosmos.
-
B.
roleInNebula
Indicates that an entity holds a specific function, position, or involvement within a particular nebula.
-
C.
roleInGalaxy
Indicates the specific function, status, or influence an entity holds within the broader structure or dynamics of a galaxy.
-
D.
roleInConstellation
Indicates the specific function or position an entity holds within a particular constellation.
-
E.
roleInAstrophysics
Indicates that an entity holds a specific professional, academic, or functional role within the field of astrophysics.
- 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_69e0b4cac7a48190a715cb3d545df2b4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c26d34bc81908bb22087d434322d |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0550ec481908a0877fb2409d983 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:37 p.m.