Triple
T19932228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ophiuchids |
E479082
|
entity |
| Predicate | typicalZenithalHourlyRate |
P94587
|
FINISHED |
| Object | few meteors per hour |
—
|
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: few meteors per hour | Statement: [Ophiuchids, typicalZenithalHourlyRate, few meteors per hour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalZenithalHourlyRate Context triple: [Ophiuchids, typicalZenithalHourlyRate, few meteors per hour]
-
A.
zenithalHourlyRate
chosen
Indicates the rate at which a quantity (typically radiant or particle flux) is received per hour when the source is positioned at the zenith directly overhead.
-
B.
typicalRate
Indicates the standard or commonly expected rate at which something occurs, is charged, or is applied in a given context.
-
C.
compensationRate
Indicates the rate or amount of payment provided in exchange for a specified unit of work, time, or service.
-
D.
humanCost
Indicates the extent of harm, suffering, or loss experienced by people as a consequence of an action, event, or decision.
-
E.
zenithUnder
Indicates that one entity is positioned directly below another entity’s highest or uppermost point.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a14a2348190b41f8e320fe661d6 |
completed | April 20, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69e537f070b481908958e0e5911dcdc1 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.