Triple
T1092391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orion |
E24193
|
entity |
| Predicate | hasDeclination |
P6950
|
FINISHED |
| Object | approximately 5 degrees |
—
|
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: approximately 5 degrees | Statement: [Orion, hasDeclination, approximately 5 degrees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDeclination Context triple: [Orion, hasDeclination, approximately 5 degrees]
-
A.
declination
chosen
Indicates the angular deviation of one direction or object from a reference plane or axis, typically measuring how far it is tilted or offset.
-
B.
declineAfter
Indicates that one entity or value decreases or worsens following another specified event, condition, or point in time.
-
C.
decliningAs
Indicates that one entity is decreasing in value, intensity, or importance relative to another over time.
-
D.
hasCaseMarking
Indicates that a linguistic element (such as a noun or pronoun) bears a specific grammatical case marking that signals its syntactic or semantic role in a clause.
-
E.
hasDefinitenessDistinction
Indicates that a language or system grammatically distinguishes between definite and indefinite (or otherwise specified) reference in its expressions.
- 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_69a49404428c819092dcc9632f5f7b8b |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b982018481908b222df095e318c0 |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b743175481908f3967e589717c55 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.