Triple
T21884383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAO 132444 |
E540367
|
entity |
| Predicate | correspondsToBD |
P111279
|
FINISHED |
| Object | +−01° 969 |
—
|
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: +−01° 969 | Statement: [SAO 132444, correspondsToBD, +−01° 969]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: correspondsToBD Context triple: [SAO 132444, correspondsToBD, +−01° 969]
-
A.
correspondsWith
Indicates that two entities are in mutual alignment or agreement, such that one matches, parallels, or is equivalent to the other in a specified respect.
-
B.
correspondsToStar
chosen
Indicates that one entity is matched or associated with a specific star as its corresponding counterpart.
-
C.
containsCorrespondenceWith
Indicates that one entity includes or holds correspondence (such as messages or communications) that is associated with or exchanged with another entity.
-
D.
equivalentTo
Indicates that two entities represent the same concept, value, or state, and can be treated as interchangeable in the given context.
-
E.
partiallyCorrespondsTo
Indicates that one entity matches or aligns with another entity only in some aspects, segments, or components, rather than fully or exactly.
- 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_69e0c479a98081908ce333853fdd4348 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f118eabb008190ab6f1364ef4e6feb |
completed | April 28, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69e6be9a65888190a66598d62d20366c |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:05 p.m.