Triple
T3729522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | (15760) 1992 QB1 |
E79026
|
entity |
| Predicate | dynamicalStatus |
P127
|
FINISHED |
| Object | dynamically stable classical KBO |
—
|
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: dynamically stable classical KBO | Statement: [(15760) 1992 QB1, dynamicalStatus, dynamically stable classical KBO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynamicalStatus Context triple: [(15760) 1992 QB1, dynamicalStatus, dynamically stable classical KBO]
-
A.
deFactoStatus
Indicates that one entity holds a role, position, or status in practice or by custom, even if it is not formally or legally recognized.
-
B.
laterStatus
Indicates that one entity represents a subsequent or resulting status or condition of another entity in time.
-
C.
status
chosen
Indicates the current condition, state, or standing of an entity within a given context.
-
D.
continuityStatus
Indicates the state of whether something continues without interruption or has been broken, paused, or reset over time.
-
E.
distributionStatus
Indicates the current state or phase of how something is being distributed, such as whether distribution is planned, in progress, completed, or halted.
- 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_69ad8b0e4650819090ad7cef094285e8 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb17432881909390284b935ed3fd |
completed | March 8, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69adc0452f5081909c79e114a86cce8c |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.