Triple
T1248828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GPS |
E26827
|
entity |
| Predicate | typicalConstellationSize |
P25781
|
FINISHED |
| Object | 24 to 32 satellites |
—
|
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: 24 to 32 satellites | Statement: [GPS, typicalConstellationSize, 24 to 32 satellites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalConstellationSize Context triple: [GPS, typicalConstellationSize, 24 to 32 satellites]
-
A.
numberOfStarsInConstellation
Indicates the numerical count of stars that belong to a given constellation.
-
B.
approximateStellarCount
Indicates an estimated or rough number of stars associated with a given astronomical object or region.
-
C.
relatedConstellation
Indicates a relationship where one entity is associated with, connected to, or corresponds to a particular constellation.
-
D.
areaRankAmongConstellations
Indicates the relative position of a constellation in an ordered list based on its sky area compared to other constellations.
-
E.
constellationFamily
Indicates that one constellation belongs to the same traditional family or grouping of constellations as another.
- F. None of above. chosen
Provenance (4 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_69a49487a9c48190ba9b05348fd1b53f |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bf827e088190a16d845cea14f2c9 |
completed | March 1, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6b075881908e867c25b5080e25 |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bc49693c8190978ec63a5171d342 |
completed | March 1, 2026, 10:23 p.m. |
Created at: March 1, 2026, 7:47 p.m.