Triple
T18776075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stephenson 2-18 |
E459136
|
entity |
| Predicate | isObscuredBy |
P22860
|
FINISHED |
| Object | interstellar dust |
—
|
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: interstellar dust | Statement: [Stephenson 2-18, isObscuredBy, interstellar dust]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isObscuredBy Context triple: [Stephenson 2-18, isObscuredBy, interstellar dust]
-
A.
obscuredIn
chosen
Indicates that one entity is hidden, blocked, or made less visible due to the presence or influence of another entity.
-
B.
isExposed
Indicates that an entity is subjected or open to the influence, effects, or presence of another entity or condition.
-
C.
isPartiallyVisibleFrom
Indicates that one entity can be seen only in part, rather than fully, from the viewpoint or location of another entity.
-
D.
isCoveredBy
Indicates that one entity is physically or conceptually overlaid, protected, or enclosed by another entity.
-
E.
overshadowedBy
Indicates that one entity’s importance, visibility, or impact is diminished because another entity is more prominent or dominant.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5933b912481908bfd97216eacb257 |
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.