Triple
T20327339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OGLE-TR-56 |
E492373
|
entity |
| Predicate | isInGalacticRegion |
P9997
|
FINISHED |
| Object | Galactic bulge direction |
—
|
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 bulge direction | Statement: [OGLE-TR-56, isInGalacticRegion, Galactic bulge direction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInGalacticRegion Context triple: [OGLE-TR-56, isInGalacticRegion, Galactic bulge direction]
-
A.
isInGalaxy
Indicates that one astronomical object is located within or belongs to a particular galaxy.
-
B.
isNearbyGalaxyOf
Indicates that one galaxy is located relatively close in space to another galaxy, within a limited cosmic distance.
-
C.
locatedInSkyRegion
chosen
Indicates that an entity is situated within or associated with a specific region or area of the sky.
-
D.
hasGalacticContext
Indicates that something is associated with, situated within, or characterized by a broader galactic-scale environment or framework.
-
E.
containsGalaxy
Indicates that one entity spatially includes or encompasses a galaxy as part of its contents or structure.
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e677e513608190b70527cd9f4d5da3 |
completed | April 20, 2026, 7 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:21 a.m.