Triple
T35629844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asteroid belt |
E1029552
|
entity |
| Predicate | KirkwoodGapsCausedBy |
P694
|
FINISHED |
| Object | orbital resonances with Jupiter |
—
|
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: orbital resonances with Jupiter | Statement: [Asteroid belt, KirkwoodGapsCausedBy, orbital resonances with Jupiter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: KirkwoodGapsCausedBy Context triple: [Asteroid belt, KirkwoodGapsCausedBy, orbital resonances with Jupiter]
-
A.
typeOfGap
Indicates the specific kind or category of gap that exists between or within entities.
-
B.
hasRingGap
Indicates that there is a discontinuity or missing segment in a ring-like structure or arrangement between the related entities.
-
C.
possibleCauseOf
Indicates that one entity is a potential, but not certain, cause or contributing factor to another entity or outcome.
-
D.
causeOf
chosen
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
E.
constructionCaused
Indicates that one construction activity, process, or project is the cause of another event, condition, or outcome.
- 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_69f76e07bb0c8190968ea2d836fc42c9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4d885881908a3612e2e75cf84f |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.