Triple
T1441585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eudora (Hyad) |
E31084
|
entity |
| Predicate | distanceContext |
P5679
|
FINISHED |
| Object | in one of the nearest prominent open clusters to Earth |
—
|
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: in one of the nearest prominent open clusters to Earth | Statement: [Eudora (Hyad), distanceContext, in one of the nearest prominent open clusters to Earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceContext Context triple: [Eudora (Hyad), distanceContext, in one of the nearest prominent open clusters to Earth]
-
A.
distance
Indicates the spatial separation or length between two points, objects, or locations.
-
B.
distanceCategory
chosen
Indicates the qualitative classification of how far apart two entities are from each other (e.g., near, medium, far).
-
C.
distanceCharacteristic
Indicates a relationship where an entity is described or constrained by some property or measure of distance (e.g., range, spacing, or separation).
-
D.
flightDistance
Indicates the measured distance covered by a flight between its origin and destination.
-
E.
distanceFromDowntown
Indicates the physical distance between a given location and the central downtown area.
- 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_69a4991633388190a4d61b5a98aa407a |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c5ff8dbc81909eafcfc9f2260a22 |
completed | March 1, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69a4c478f65481909ee716791c663491 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.