Triple
T10697317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sigma Capricornids |
E252177
|
entity |
| Predicate | meteoroidOrigin |
P69252
|
FINISHED |
| Object | cometary debris |
—
|
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: cometary debris | Statement: [Sigma Capricornids, meteoroidOrigin, cometary debris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meteoroidOrigin Context triple: [Sigma Capricornids, meteoroidOrigin, cometary debris]
-
A.
meteoroidSource
chosen
Indicates that one entity is the origin or source from which the meteoroid represented by the other entity comes.
-
B.
viewOnMeteorites
Indicates a stance, opinion, or perspective that an entity holds regarding meteorites.
-
C.
meteorShowers
Indicates that one or more meteor showers occur, are present, or are being observed in relation to the specified entities.
-
D.
orbitsBeyond
Indicates that one celestial body orbits at a greater average distance from a central object than another specified body.
-
E.
relatedMeteorShowers
Indicates that two or more meteor showers are connected by a meaningful relationship, such as sharing a common origin, time period, or observational characteristics.
- 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_69d6aa5cbabc8190973e683950d89faf |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fd89390c8190969ab2b4a79d5818 |
completed | April 9, 2026, 1:14 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8cc0788190b4c02a772e4b58b3 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:12 p.m.