Triple
T19931945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cygnus X complex |
E479073
|
entity |
| Predicate | oneOfNearest |
P94762
|
FINISHED |
| Object | massive star-forming complexes 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: massive star-forming complexes to Earth | Statement: [Cygnus X complex, oneOfNearest, massive star-forming complexes to Earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oneOfNearest Context triple: [Cygnus X complex, oneOfNearest, massive star-forming complexes to Earth]
-
A.
nearestPass
Indicates that one entity is the closest in distance or proximity to another entity compared to all other possible entities or paths.
-
B.
shortestNear
chosen
Indicates that one entity is the closest (or among the closest) to another entity compared to other nearby alternatives.
-
C.
nearbyTo
Indicates that one entity is located close in distance or position to another entity.
-
D.
closestTo
Indicates that one entity is nearer in distance to a reference entity than any other comparable entity.
-
E.
closerTo
Indicates that one entity is at a smaller distance to a reference entity than another entity is.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a14a2348190b41f8e320fe661d6 |
completed | April 20, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69e537f070b481908958e0e5911dcdc1 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.