Triple
T33829946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 169P/NEAT |
E867067
|
entity |
| Predicate | hasMeteorStream |
P198583
|
FINISHED |
| Object | Alpha Capricornid meteoroid stream |
—
|
NE NERFINISHED |
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: Alpha Capricornid meteoroid stream | Statement: [169P/NEAT, hasMeteorStream, Alpha Capricornid meteoroid stream]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMeteorStream Context triple: [169P/NEAT, hasMeteorStream, Alpha Capricornid meteoroid stream]
-
A.
meteorStreamType
Indicates the classification or category of a meteor stream based on its physical or observational characteristics.
-
B.
hasStreaming
Indicates that an entity provides or supports streaming access to another entity (such as media, data, or content).
-
C.
meteorShower
Indicates an event where numerous meteors enter a planet’s atmosphere in a short period, typically appearing as a concentrated display of shooting stars.
-
D.
meteorType
Indicates the classification or category of a meteor based on its type.
-
E.
hasFlux
Indicates that one entity exhibits or is characterized by a flow, rate of transfer, or continuous change with respect to another entity or quantity.
- F. None of above. chosen
Provenance (4 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_69f34991dd248190a659541588506b3c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fef3ceef648190b58027c93d757438 |
completed | May 9, 2026, 8:43 a.m. |
| PD | Predicate disambiguation | batch_69fef359da2c819091a034387b08821f |
completed | May 9, 2026, 8:42 a.m. |
| PDg | Predicate description generation | batch_69fef3cdea708190af41c1ff23b68f88 |
completed | May 9, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:46 a.m.