Triple
T633421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuiper Belt object |
E15968
|
entity |
| Predicate | hasDynamicalClass |
P17318
|
FINISHED |
| Object | classical Kuiper Belt object |
—
|
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: classical Kuiper Belt object | Statement: [Kuiper Belt object, hasDynamicalClass, classical Kuiper Belt object]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDynamicalClass Context triple: [Kuiper Belt object, hasDynamicalClass, classical Kuiper Belt object]
-
A.
hasServiceClass
Indicates that an entity is associated with, or categorized under, a particular class or type of service.
-
B.
hasHigherClass
Indicates that one entity belongs to a higher rank, level, or category in a hierarchy than another entity.
-
C.
hasDerivative
Indicates that one entity is derived, obtained, or produced from another through some transformation, process, or modification.
-
D.
hasDependency
Indicates that one entity relies on or requires another entity in order to function, exist, or be fulfilled.
-
E.
hasFiveClassStructure
Indicates that an entity is organized into, or conforms to, a structure consisting of five distinct classes.
- 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_69a4935c131c8190a5378c6bf101e8cc |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49ec3b6488190aa0dce216c089a2e |
completed | March 1, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69a49d030c648190ba1a02301b45f694 |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49defe58c8190bd39ef47c9f660a7 |
completed | March 1, 2026, 8:13 p.m. |
Created at: March 1, 2026, 7:35 p.m.