Triple
T36879929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubble G |
E911450
|
entity |
| Predicate | isDifficultToObserveFrom |
P147891
|
FINISHED |
| Object | Earth |
—
|
NE NERFINISHED |
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: Earth | Statement: [Hubble G, isDifficultToObserveFrom, Earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDifficultToObserveFrom Context triple: [Hubble G, isDifficultToObserveFrom, Earth]
-
A.
isDifficultToSeeFrom
chosen
Indicates that one entity is hard to visually perceive or observe when viewed from the vantage point or location of another entity.
-
B.
isDifficultToObserveInVisible
Indicates that the subject cannot be easily detected or studied using visible-wavelength (optical) observations.
-
C.
visibleFromEarth
Indicates that the object can be observed from Earth, either with the naked eye or with appropriate instruments, under suitable viewing conditions.
-
D.
canBeSeenFromEarthWith
Indicates that one entity is visible from Earth using the specified instrument, method, or observational aid.
-
E.
observingDifficultyRange
Indicates the range or spectrum of difficulty levels associated with observing or detecting something.
- 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_69f76e82339881909607a65c0503d941 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd68f6988190abe4a5471d0876e8 |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.