Triple
T37098664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bárðarbunga |
E918634
|
entity |
| Predicate | hasLavaField |
P201122
|
FINISHED |
| Object | Holuhraun |
—
|
NE NERFINISHED |
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: Holuhraun | Statement: [Bárðarbunga, hasLavaField, Holuhraun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLavaField Context triple: [Bárðarbunga, hasLavaField, Holuhraun]
-
A.
hasFieldName
Indicates that one entity is associated with, or identified by, a specific field name in a data structure or schema.
-
B.
hasBaseField
Indicates that one entity serves as the foundational or underlying field structure upon which another entity is defined or constructed.
-
C.
hasStaticField
Indicates that one entity declares or owns a static (class-level) field that is associated with it.
-
D.
hasFieldContribution
Indicates that an entity has made a contribution or provided input within a particular field, domain, or area of activity.
-
E.
hasRichFieldOf
Indicates that one entity possesses or is characterized by an abundant or highly developed presence of another specified attribute, resource, or domain.
- 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_69f76e9a48bc8190a3947508d8bca408 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffc89596d08190b97bd60b45c7f9c0 |
completed | May 9, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69ffc81ba5dc8190ae94d44e2284948f |
completed | May 9, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ffc894cef481908dae1d9cdc7d9d1f |
completed | May 9, 2026, 11:51 p.m. |
Created at: May 3, 2026, 4:14 p.m.