Triple
T18443823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 6520 |
E450602
|
entity |
| Predicate | projectedAgainst |
P29992
|
FINISHED |
| Object | rich Milky Way star fields |
—
|
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: rich Milky Way star fields | Statement: [NGC 6520, projectedAgainst, rich Milky Way star fields]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: projectedAgainst Context triple: [NGC 6520, projectedAgainst, rich Milky Way star fields]
-
A.
isInDirectionOf
chosen
Indicates that one entity is oriented or positioned toward the direction in which another entity lies.
-
B.
orientedParallelTo
Indicates that one entity is parallel to another with a specified or consistent direction or orientation.
-
C.
perpendicularTo
Indicates that one entity is oriented at a right angle (90 degrees) to another entity.
-
D.
projectionAngle
Indicates the angle at which one entity is projected onto or relative to another reference (such as a line, plane, or direction).
-
E.
associatedPlane
Indicates a relationship where one entity is linked or connected to a specific plane, typically as the plane it uses, refers to, or is defined with respect to.
- 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51c12a0248190a848a1fe833a1975 |
completed | April 19, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69e469c943a4819094c8fdc5971ad3a7 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:30 a.m.