Triple
T36564007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1939 Quetta |
E901921
|
entity |
| Predicate | hasDynamicalType |
P17318
|
FINISHED |
| Object | main-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: main-belt object | Statement: [1939 Quetta, hasDynamicalType, main-belt object]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDynamicalType Context triple: [1939 Quetta, hasDynamicalType, main-belt object]
-
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.
isDynamicallyTyped
Indicates that a programming language determines variable types at runtime rather than at compile time.
-
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.
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.
-
E.
hasFamilyDynamic
Indicates the type or nature of the interpersonal relationships and interaction patterns that exist within a family unit.
- 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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.