Triple
T21246821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1835 eruption of Cosigüina |
E523632
|
entity |
| Predicate | vei |
P143357
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [1835 eruption of Cosigüina, vei, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vei Context triple: [1835 eruption of Cosigüina, vei, 5]
-
A.
via
Indicates that something occurs, is achieved, or is connected by means of, through the use of, or along the route of another entity or medium.
-
B.
vise
Indicates that one entity firmly grips, clamps, or holds another in place, typically restricting its movement or separating it from other objects.
-
C.
eve
Indicates a relationship where one entity is the evening or night-time counterpart, phase, or occurrence associated with another entity.
-
D.
vice
Indicates a relationship where one entity serves as the deputy, subordinate leader, or second-in-command to another entity in a hierarchical structure.
-
E.
roadSide
Indicates that one entity is located along, beside, or immediately adjacent to a road.
- 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_69e0b5146c108190adc9adb73e90abff |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7359abdac81908b74dad1b8cc0aa9 |
completed | April 21, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69e5f61239708190ab7b3c83ae848a0d |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f9943ed881909ef49045c5bcf6df |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 3:54 p.m.