Triple
T33829587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eta Aquariids |
E867058
|
entity |
| Predicate | showerActivityClass |
P177750
|
FINISHED |
| Object | strong |
—
|
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: strong | Statement: [Eta Aquariids, showerActivityClass, strong]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: showerActivityClass Context triple: [Eta Aquariids, showerActivityClass, strong]
-
A.
showerType
Indicates the specific kind or category of shower associated with an entity (e.g., walk-in, bathtub-shower combo, outdoor shower).
-
B.
showerFamily
Indicates that one entity takes a shower together with, or in the presence of, members of their family.
-
C.
hasWaterActivity
Indicates that one entity possesses, exhibits, or is characterized by a particular level or type of water-related activity (such as moisture content, water availability, or water-based processes).
-
D.
hasWaterRelatedActivity
Indicates that an entity engages in, offers, or is associated with an activity involving water (e.g., swimming, boating, or other water-based actions).
-
E.
typeOfBathingSite
Indicates the specific kind or category of bathing site associated with a given location or facility.
- 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_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: May 1, 2026, 1:46 a.m.