Triple
T19133128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | (386723) 2009 YE7 |
E468363
|
entity |
| Predicate | hasDynamicalStatus |
P17318
|
FINISHED |
| Object | classical TNO |
—
|
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 TNO | Statement: [(386723) 2009 YE7, hasDynamicalStatus, classical TNO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDynamicalStatus Context triple: [(386723) 2009 YE7, hasDynamicalStatus, classical TNO]
-
A.
hasDynamicalClass
chosen
Indicates that an entity belongs to a specific category defined by its dynamical or motion-related behavior (e.g., orbital or kinematic characteristics).
-
B.
hasDynamics
Indicates that one entity exhibits or is characterized by specific dynamic behavior, changes, or variations over time in relation to another entity or context.
-
C.
isPartOfDynamically
Indicates that one entity is currently a component or member of another entity in a way that can change over time or at runtime.
-
D.
hasStatusBasedOn
Indicates that an entity’s status is determined or derived from another condition, event, or entity.
-
E.
hasDutyStatus
Indicates that an entity currently holds a particular duty or operational status in relation to a role, task, or assignment.
- 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e3ea82f08190811ef35fbae744d1 |
completed | April 20, 2026, 8:29 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b085288190b974d649e12e0844 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.