Triple
T38281789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ptolemaic magnitude scale |
E1022097
|
entity |
| Predicate | classRangeUpperBound |
P128035
|
FINISHED |
| Object | 6 |
—
|
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: 6 | Statement: [Ptolemaic magnitude scale, classRangeUpperBound, 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classRangeUpperBound Context triple: [Ptolemaic magnitude scale, classRangeUpperBound, 6]
-
A.
includesUpperBound
chosen
Indicates that the specified range or interval contains and counts its upper limit value as part of the set.
-
B.
isUpperBoundFor
Indicates that one value is greater than or equal to every element in a given set or collection, serving as an upper limit for them.
-
C.
upperBoundaryType
Indicates the kind or classification of the upper boundary that limits or caps a given range, interval, or extent.
-
D.
isHighestRangeOf
Indicates that one entity represents the maximum or topmost range or interval within which another entity falls or is categorized.
-
E.
upperBoundaryGSSPLocation
Indicates the relationship where a location serves as the upper boundary or limit of a GSSP (Global Boundary Stratotype Section and Point) definition.
- 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_69f76df0cddc81908d16c1556ff4097f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
Created at: May 3, 2026, 4:30 p.m.