Triple
T5259864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CMa Dwarf |
E118796
|
entity |
| Predicate | obscuredBy |
P22860
|
FINISHED |
| Object | Galactic disk |
—
|
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: Galactic disk | Statement: [CMa Dwarf, obscuredBy, Galactic disk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: obscuredBy Context triple: [CMa Dwarf, obscuredBy, Galactic disk]
-
A.
obscuredIn
chosen
Indicates that one entity is hidden, blocked, or made less visible due to the presence or influence of another entity.
-
B.
overshadowedBy
Indicates that one entity’s importance, visibility, or impact is diminished because another entity is more prominent or dominant.
-
C.
partlyCoveredBy
Indicates that one entity is covered or overlapped by another entity, but only to a partial extent rather than completely.
-
D.
visibleAt
Indicates that one entity can be seen or perceived from a specific location, viewpoint, or context at a given time.
-
E.
locatedBehind
Indicates that one entity is positioned at the rear of or on the far side of another entity along a given viewing or reference direction.
- 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_69bd446a42c88190b7ecbef006561d55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7bcced6881909bdb7ac5471a37fe |
completed | March 20, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69bd77c55224819096c0bcfcfae79bd3 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:50 p.m.