Triple
T3839721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1036 Ganymed |
E93420
|
entity |
| Predicate | belongsToDynamicalGroup |
P12263
|
FINISHED |
| Object | near-Earth 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: near-Earth asteroids | Statement: [1036 Ganymed, belongsToDynamicalGroup, near-Earth asteroids]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToDynamicalGroup Context triple: [1036 Ganymed, belongsToDynamicalGroup, near-Earth asteroids]
-
A.
belongsToGroup
chosen
Indicates that an entity is a member of, or is included within, a particular group or collection.
-
B.
hasRelatedGroup
Indicates that one group or collection is associated with another group or collection through some defined relationship or connection.
-
C.
hasSubsidiaryRoleInGroup
Indicates that an entity holds a secondary or supporting role within a specified group.
-
D.
belongsToBlock
Indicates that something is a member or component of a specific block or grouping.
-
E.
canBelongTo
Indicates that something is capable of being a member or part of a particular group, category, or owner.
- 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_69aed96ce578819084ab16e3439976c9 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeeba1535c8190b36e2ab2d4514b54 |
completed | March 9, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69aee74dcecc819098285483ec721b40 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:18 p.m.