Triple
T25736513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catatumbo lightning |
E645390
|
entity |
| Predicate | averageDurationPerNight |
P152308
|
FINISHED |
| Object | up to 9 hours per night |
—
|
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: up to 9 hours per night | Statement: [Catatumbo lightning, averageDurationPerNight, up to 9 hours per night]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: averageDurationPerNight Context triple: [Catatumbo lightning, averageDurationPerNight, up to 9 hours per night]
-
A.
typicalRuntimePerNight
chosen
Indicates the usual amount of time something runs or operates during a single night.
-
B.
typicalDurationDays
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
-
C.
typicalRate
Indicates the standard or commonly expected rate at which something occurs, is charged, or is applied in a given context.
-
D.
economyRate
Indicates the rate or level of economic performance, activity, or growth associated with the related entities.
-
E.
banDurationApproximate
Indicates that the duration of a ban is known only approximately rather than as an exact, precise time period.
- 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_69e77e85254081908d79ee4e8715f283 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fcbf71308190a81518c504d5632d |
completed | May 2, 2026, 1:31 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 11:27 p.m.