Triple
T10586477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piscis Austrinus |
E249866
|
entity |
| Predicate | meteorShowers |
P94780
|
FINISHED |
| Object | Piscis Austrinids |
—
|
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: Piscis Austrinids | Statement: [Piscis Austrinus, meteorShowers, Piscis Austrinids]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meteorShowers Context triple: [Piscis Austrinus, meteorShowers, Piscis Austrinids]
-
A.
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.
-
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.
meteorBrightness
Indicates the observed luminous intensity or apparent brightness of a meteor during its visible passage.
-
D.
meteoroidSource
Indicates that one entity is the origin or source from which the meteoroid represented by the other entity comes.
-
E.
marksAstronomicalEvent
Indicates that one entity serves as a sign, boundary, or reference point denoting the occurrence or timing of an astronomical event.
- 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_69d381c9d3d48190a29ee491e1696a0e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d527698be48190a2f5e573d7cc0661 |
completed | April 7, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69d51907b2b881908ab9a8594688ee06 |
completed | April 7, 2026, 2:47 p.m. |
| PDg | Predicate description generation | batch_69d5270eca0481908573b698390c5b08 |
completed | April 7, 2026, 3:47 p.m. |
Created at: April 6, 2026, 12:39 p.m.