Triple
T12370475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 7319 |
E294985
|
entity |
| Predicate | isInSkyRegion |
P9997
|
FINISHED |
| Object | near Stephan's Quintet field |
—
|
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: near Stephan's Quintet field | Statement: [NGC 7319, isInSkyRegion, near Stephan's Quintet field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInSkyRegion Context triple: [NGC 7319, isInSkyRegion, near Stephan's Quintet field]
-
A.
locatedInSkyRegion
chosen
Indicates that an entity is situated within or associated with a specific region or area of the sky.
-
B.
isOneOfIAU88Constellations
Indicates that an entity belongs to the official set of 88 constellations recognized by the International Astronomical Union (IAU).
-
C.
isInArea
Indicates that one entity is located within the spatial bounds or region defined by another entity.
-
D.
meetsInRegion
Indicates that two or more entities encounter or come together within a specified geographic or spatial region.
-
E.
hasOrbitalRegion
Indicates that one entity occupies, lies within, or is associated with a specific orbital zone or region around another body.
- 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_69d6ab6d8a4081908636601e69ddf262 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d942a2d6e08190a13c7ff89af09354 |
completed | April 10, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69d93ecf6b548190a394b6b56a0c1c68 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:54 p.m.