Triple
T35629835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asteroid belt |
E1029552
|
entity |
| Predicate | approximateNumberOfKnownAsteroids |
P200014
|
FINISHED |
| Object | over 1 million |
—
|
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: over 1 million | Statement: [Asteroid belt, approximateNumberOfKnownAsteroids, over 1 million]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateNumberOfKnownAsteroids Context triple: [Asteroid belt, approximateNumberOfKnownAsteroids, over 1 million]
-
A.
approximateStellarCount
Indicates an estimated or rough number of stars associated with a given astronomical object or region.
-
B.
approximateNumberOfObjectsLargerThan1km
Indicates an estimated count of objects whose size exceeds 1 kilometer.
-
C.
minorPlanetNumber
Indicates the unique numerical designation assigned to a minor planet within the catalog of such celestial bodies.
-
D.
hasApproximateNumberOfKnownMoons
Indicates that an entity is associated with an estimated or non-exact count of moons known to orbit it.
-
E.
hasApproximateAbsoluteMagnitude
Indicates that an entity is associated with an estimated value of its absolute magnitude, rather than a precisely measured one.
- 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_69f76e07bb0c8190968ea2d836fc42c9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff6a4ce9a08190b98abde3a170dd69 |
completed | May 9, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69ff69c11634819089d1084bd2c11534 |
completed | May 9, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69ff6a4c32dc819097f591944bee8851 |
completed | May 9, 2026, 5:09 p.m. |
Created at: May 3, 2026, 4:05 p.m.