Triple
T18774638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UGC 452 |
E459103
|
entity |
| Predicate | isNearestOfType |
P120316
|
FINISHED |
| Object | one of the nearest elliptical galaxies |
—
|
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: one of the nearest elliptical galaxies | Statement: [UGC 452, isNearestOfType, one of the nearest elliptical galaxies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNearestOfType Context triple: [UGC 452, isNearestOfType, one of the nearest elliptical galaxies]
-
A.
closestTo
Indicates that one entity is nearer in distance to a reference entity than any other comparable entity.
-
B.
isNearestMajorRangeTo
Indicates that one range is the closest significant (major) range in distance or proximity to another specified location or entity.
-
C.
isCloseTo
Indicates that one entity is physically or conceptually near another, within a relatively short distance or range.
-
D.
isNavigableNear
Indicates that an entity can be traversed or passed through in close proximity to another specified entity or location.
-
E.
hasNearbySiteType
chosen
Indicates that one entity has another entity of a specified site type located in its close physical vicinity.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5933888408190a21f9ac5b360d1eb |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d1126e4819099607837ed5aadca |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.