Triple
T13689991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carme group |
E328234
|
entity |
| Predicate | hasParentBodyHypothesis |
P111180
|
FINISHED |
| Object | single captured D-type asteroid |
—
|
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: single captured D-type asteroid | Statement: [Carme group, hasParentBodyHypothesis, single captured D-type asteroid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentBodyHypothesis Context triple: [Carme group, hasParentBodyHypothesis, single captured D-type asteroid]
-
A.
hasParentBodyMinorPlanetNumber
Indicates that one entity is associated with the minor planet number assigned to its parent celestial body.
-
B.
belongsToBody
Indicates that something is a part of, or under the ownership/authority of, a particular body or organization.
-
C.
hasParentAwardBody
Indicates that an award is associated with or governed by a higher-level parent awarding body or organization.
-
D.
hasParentSystem
Indicates that one system is hierarchically contained within or derived from another, which serves as its parent system.
-
E.
hasBodyOf
Indicates that one entity possesses, contains, or is composed of the physical body or main substance of another entity.
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc6721c248190ac48491b5f39c8f0 |
completed | April 12, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59ca1a88190a6abd3bd00554c93 |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 9:53 p.m.