Triple
T29860486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 5668 Foucault |
E758298
|
entity |
| Predicate | belongsToAstronomicalPopulation |
P51233
|
FINISHED |
| Object | main-belt asteroids |
—
|
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: main-belt asteroids | Statement: [5668 Foucault, belongsToAstronomicalPopulation, main-belt asteroids]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToAstronomicalPopulation Context triple: [5668 Foucault, belongsToAstronomicalPopulation, main-belt asteroids]
-
A.
belongsToPopulation
chosen
Indicates that an entity is a member or constituent of a specified population or group.
-
B.
belongsToStarCluster
Indicates that an astronomical object is a member of, or gravitationally bound to, a specific star cluster.
-
C.
containsStellarPopulation
Indicates that one astronomical object includes or encompasses a group of stars as part of its stellar content.
-
D.
stellarPopulation
Indicates a relationship where one entity represents the group or distribution of stars (stellar population) associated with another entity, such as a galaxy or region of space.
-
E.
hasStarClusterPopulation
Indicates that an entity possesses or is associated with a population of star clusters.
- 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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fdb04ed81c8190b8feea90c1c785a6 |
completed | May 8, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69fda9d6c5148190a63205b6d9b0a1b4 |
completed | May 8, 2026, 9:16 a.m. |
Created at: April 29, 2026, 5:48 p.m.