Triple
T19261229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uranometria |
E481653
|
entity |
| Predicate | usesMagnitudeScale |
P1938
|
FINISHED |
| Object | stellar magnitude |
—
|
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: stellar magnitude | Statement: [Uranometria, usesMagnitudeScale, stellar magnitude]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMagnitudeScale Context triple: [Uranometria, usesMagnitudeScale, stellar magnitude]
-
A.
magnitudeScale
chosen
Indicates the scale or measurement system used to quantify the magnitude or intensity of something.
-
B.
usesScaleDegrees
Indicates that something is expressed, analyzed, or organized in terms of musical scale degrees rather than absolute pitches.
-
C.
hasMagnitudeProperty
Indicates that an entity is associated with a quantitative magnitude-related property, such as size, intensity, or amount.
-
D.
hasScale
Indicates that one entity possesses or is characterized by a scale or graduated measurement system related to another entity.
-
E.
exampleMagnitude
Indicates a relationship where one entity serves as a representative or typical instance that illustrates the scale, size, or intensity (magnitude) of another entity or quantity.
- 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb890e7c8190beba407f63459382 |
completed | April 20, 2026, 10:10 a.m. |
| PD | Predicate disambiguation | batch_69e4dd002d00819088b625056edfb74e |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:28 p.m.