Triple
T16200451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MPC database |
E393183
|
entity |
| Predicate | centralCatalogFor |
P122136
|
FINISHED |
| Object | minor planets |
—
|
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: minor planets | Statement: [MPC database, centralCatalogFor, minor planets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralCatalogFor Context triple: [MPC database, centralCatalogFor, minor planets]
-
A.
centralEntity
Indicates that the subject serves as the primary or most important entity around which related entities, actions, or information are organized.
-
B.
centralIn
Indicates that one entity occupies a central or most important position within another entity, context, or structure.
-
C.
centralRepertoireFor
Indicates that something serves as a primary or core collection of works, items, or elements for a particular entity or context.
-
D.
centerType
Indicates the classification or category of a center (e.g., type of facility, institution, or hub) associated with an entity.
-
E.
centralName
Indicates that the specified name serves as the primary or main identifying label within a given context or naming structure.
- 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e22709b0d88190b40787e0520d02ab |
completed | April 17, 2026, 12:26 p.m. |
| PD | Predicate disambiguation | batch_69e219e11f6081909106b1240a17fd37 |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e55a2388190b29a045a8c608ba4 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:03 a.m.