Triple
T18771213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lupus |
E459019
|
entity |
| Predicate | meteorShowersAssociated |
P94780
|
FINISHED |
| Object | none prominent |
—
|
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: none prominent | Statement: [Lupus, meteorShowersAssociated, none prominent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meteorShowersAssociated Context triple: [Lupus, meteorShowersAssociated, none prominent]
-
A.
meteorShowers
chosen
Indicates that one or more meteor showers occur, are present, or are being observed in relation to the specified entities.
-
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.
meteorShowerRadiant
Indicates the apparent point in the sky from which the meteors in a meteor shower seem to originate.
-
D.
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.
-
E.
meteorBrightness
Indicates the observed luminous intensity or apparent brightness of a meteor during its visible passage.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e59335a01881908731371be1e27a6b |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.