Triple
T29883593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 4372 |
E758948
|
entity |
| Predicate | heavilyObscuredBy |
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: [NGC 4372, heavilyObscuredBy, interstellar dust]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heavilyObscuredBy Context triple: [NGC 4372, heavilyObscuredBy, 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.
isObscureFigureIn
Indicates that an entity is a little-known or not widely recognized figure within a particular context, field, or domain.
-
C.
partlyCoveredBy
Indicates that one entity is covered or overlapped by another entity, but only to a partial extent rather than completely.
-
D.
viewedAsObstacleBy
Indicates that one entity is perceived or treated as an obstacle or hindrance by another entity.
-
E.
isDifficultToSeeFrom
Indicates that one entity is hard to visually perceive or observe when viewed from the vantage point or location of another entity.
- 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_69f2245de2f48190a481404896b56254 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f676fb3b9c819097dcd5920e0cd09e |
completed | May 2, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:58 p.m.