Triple
T10489191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alpha Capricornids |
E247368
|
entity |
| Predicate | typicalObservationRate |
P57967
|
FINISHED |
| Object | a few meteors per hour at peak |
—
|
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: a few meteors per hour at peak | Statement: [Alpha Capricornids, typicalObservationRate, a few meteors per hour at peak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalObservationRate Context triple: [Alpha Capricornids, typicalObservationRate, a few meteors per hour at peak]
-
A.
typicalUpdateFrequency
Indicates how often an entity is usually updated or refreshed over time.
-
B.
inspectionFrequency
Indicates how often an entity is examined, checked, or reviewed within a given time period.
-
C.
typicalPeriod
Indicates the usual or characteristic time interval or duration associated with an event, process, or state.
-
D.
canObserveFrequency
Indicates that one entity has the capability to detect, measure, or monitor the frequency of another entity or signal.
-
E.
typicalMeasure
chosen
Indicates the standard or characteristic quantitative measure typically associated with something, such as its usual size, weight, duration, or other magnitude.
- 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_69d381c309b88190af78aa681cf6a4c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5097ca5c081908b47a08ca7885650 |
completed | April 7, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8a30848190b33cf43f005a028e |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:23 p.m.