Triple
T869116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milky Way center |
E18770
|
entity |
| Predicate | observationDifficulty |
P11058
|
FINISHED |
| Object | obscured by 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: obscured by dust | Statement: [Milky Way center, observationDifficulty, obscured by dust]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observationDifficulty Context triple: [Milky Way center, observationDifficulty, obscured by dust]
-
A.
difficulty
Indicates the level of challenge, complexity, or effort required to perform an action, solve a problem, or achieve a particular outcome.
-
B.
observationType
Indicates the specific kind or category of observation being made or recorded in a given context.
-
C.
difficultyRelativeTo
Indicates that one entity’s level of difficulty is being compared to and expressed in relation to another entity’s level of difficulty.
-
D.
hasMeasurementDifficulty
Indicates that performing a measurement on something is challenging or problematic in some way.
-
E.
isDifficultToAccessBecauseOf
chosen
Indicates that something is hard to reach, obtain, or use due to a specified obstacle, condition, or circumstance.
- 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_69a4ac811e548190a72b7a10b5ea8665 |
completed | March 1, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69a4aa89ca008190b50d061ac7fe19f9 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.