Triple
T18772088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HD 24131 |
E459037
|
entity |
| Predicate | hasGalacticEnvironment |
P29993
|
FINISHED |
| Object | OB association |
—
|
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: OB association | Statement: [HD 24131, hasGalacticEnvironment, OB association]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGalacticEnvironment Context triple: [HD 24131, hasGalacticEnvironment, OB association]
-
A.
hasGalacticContext
chosen
Indicates that something is associated with, situated within, or characterized by a broader galactic-scale environment or framework.
-
B.
isInGalaxy
Indicates that one astronomical object is located within or belongs to a particular galaxy.
-
C.
containsGalaxy
Indicates that one entity spatially includes or encompasses a galaxy as part of its contents or structure.
-
D.
galacticNeighborhood
Indicates a spatial relationship where one astronomical object or system is located in the nearby region or vicinity of another within a galaxy or local group of galaxies.
-
E.
stellarEnvironment
Indicates the surrounding physical and spatial conditions associated with a star, such as its nearby matter, radiation fields, and local cosmic 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e59336a6b08190819595a55177264e |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d1126e4819099607837ed5aadca |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.