Triple
T6175345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iota Cancrids |
E137803
|
entity |
| Predicate | meteoroidSource |
P69252
|
FINISHED |
| Object | cometary or asteroidal (uncertain) |
—
|
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 or asteroidal (uncertain) | Statement: [Iota Cancrids, meteoroidSource, cometary or asteroidal (uncertain)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meteoroidSource Context triple: [Iota Cancrids, meteoroidSource, cometary or asteroidal (uncertain)]
-
A.
viewOnMeteorites
Indicates a stance, opinion, or perspective that an entity holds regarding meteorites.
-
B.
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.
-
C.
orbitsBeyond
Indicates that one celestial body orbits at a greater average distance from a central object than another specified body.
-
D.
cosmicBodies
Indicates a relationship in which entities are identified as astronomical or celestial objects existing in outer space.
-
E.
scienceReturn
Indicates that an action or process yields scientific data, findings, or value as its outcome.
- 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_69c008a80f748190ba3d07ffc81acb29 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05dc70ac481909fd1db0d69837eca |
completed | March 22, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c055f7f12881908e21c04e9b752ba4 |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c056df95ac8190bc5efe050d3af864 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:18 p.m.