Triple
T868852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Local Interstellar Cloud |
E18765
|
entity |
| Predicate | isEmbeddedIn |
P11236
|
FINISHED |
| Object | hot low-density gas of the Local Bubble |
—
|
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: hot low-density gas of the Local Bubble | Statement: [Local Interstellar Cloud, isEmbeddedIn, hot low-density gas of the Local Bubble]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEmbeddedIn Context triple: [Local Interstellar Cloud, isEmbeddedIn, hot low-density gas of the Local Bubble]
-
A.
canBeEmbeddedIn
Indicates that one entity can be inserted or integrated within another entity, typically preserving structure or compatibility.
-
B.
isReferencedIn
Indicates that one entity is cited, mentioned, or otherwise referred to within another entity.
-
C.
isPartOfType
Indicates that one type or category is a constituent or subset within a larger, encompassing type or category.
-
D.
integratedIn
Indicates that one entity is incorporated as a component or part within a larger system, structure, or context represented by another entity.
-
E.
includesElement
chosen
Indicates that one collection, set, or structure contains a specified element as a member or component.
- 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_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. |
Created at: March 1, 2026, 7:39 p.m.