Triple
T20282034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pisces II Dwarf Galaxy |
E503171
|
entity |
| Predicate | isDifficultToDetect |
P132950
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Pisces II Dwarf Galaxy, isDifficultToDetect, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDifficultToDetect Context triple: [Pisces II Dwarf Galaxy, isDifficultToDetect, true]
-
A.
isDifficultToObserveInVisible
chosen
Indicates that the subject cannot be easily detected or studied using visible-wavelength (optical) observations.
-
B.
difficultToAnalyzeAs
Indicates that one entity is hard to examine, interpret, or understand when considered in terms of, or compared to, another entity.
-
C.
detected
Indicates that an entity has observed, identified, or discovered the presence or occurrence of another entity or event.
-
D.
isDifficultToAccess
Indicates that reaching, using, or obtaining the referenced entity requires significant effort, obstacles, or special conditions.
-
E.
isDifficultToAccessBecauseOf
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_69e0b4b0e79c8190bd61f22ef1329fa8 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6768f86448190842389a98b93a918 |
completed | April 20, 2026, 6:55 p.m. |
| PD | Predicate disambiguation | batch_69e55b1e5e1c8190ba8a5544b1db9e1d |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 10:39 a.m.