Triple
T33829571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eta Aquariids |
E867058
|
entity |
| Predicate | typicalMeteorSpeed |
P94585
|
FINISHED |
| Object | about 66 km/s |
—
|
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: about 66 km/s | Statement: [Eta Aquariids, typicalMeteorSpeed, about 66 km/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMeteorSpeed Context triple: [Eta Aquariids, typicalMeteorSpeed, about 66 km/s]
-
A.
meteorVelocity
chosen
Indicates the speed and direction at which a meteor is moving through space or an atmosphere.
-
B.
meteorVelocityCategory
Indicates the classification of a meteor based on the speed at which it is traveling.
-
C.
meteorBrightness
Indicates the observed luminous intensity or apparent brightness of a meteor during its visible passage.
-
D.
meteoriteStruck
Indicates that a meteorite collided with and impacted a particular target or location.
-
E.
typicalZHR
Indicates the typical zenithal hourly rate, i.e., the usual number of observable events per hour under ideal viewing conditions when the radiant is at the zenith.
- 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_69f34991dd248190a659541588506b3c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:46 a.m.