Triple
T21523193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geminids |
E531026
|
entity |
| Predicate | IAUShowerCode |
P144705
|
FINISHED |
| Object | GEM |
—
|
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: GEM | Statement: [Geminids, IAUShowerCode, GEM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IAUShowerCode Context triple: [Geminids, IAUShowerCode, GEM]
-
A.
meteorShowerRadiant
Indicates the apparent point in the sky from which the meteors in a meteor shower seem to originate.
-
B.
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.
-
C.
hasCaldwellNumber
Indicates that an astronomical object is associated with a specific entry in the Caldwell catalog, identified by its Caldwell number.
-
D.
meteorShowers
Indicates that one or more meteor showers occur, are present, or are being observed in relation to the specified entities.
-
E.
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.
- 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_69e0c45d95a081908e7962ad215da746 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee884db3ac81909e77d22d607ac72d |
completed | April 26, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69e6320043bc81909417c41a718652ba |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e6386c5a4481909c37f7de7e9fc025 |
completed | April 20, 2026, 2:30 p.m. |
Created at: April 16, 2026, 6:26 p.m.