Triple
T35437515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1994 Rabaul eruption |
E1024249
|
entity |
| Predicate | ashAffectedArea |
P1586
|
FINISHED |
| Object | New Britain |
—
|
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: New Britain | Statement: [1994 Rabaul eruption, ashAffectedArea, New Britain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ashAffectedArea Context triple: [1994 Rabaul eruption, ashAffectedArea, New Britain]
-
A.
affectedArea
chosen
Indicates the specific region or extent over which an event, condition, or influence has an impact.
-
B.
affectedLand
Indicates that a piece of land is impacted or influenced by a particular event, action, or condition.
-
C.
areaOfSupport
Indicates the spatial region or domain within which an entity provides support, assistance, or backing to another.
-
D.
coveredArea
Indicates that one entity occupies or extends over a specific spatial region or surface area associated with another entity.
-
E.
areaProtected
Indicates that a specified geographic area is designated and managed as protected, typically restricting certain activities to conserve its natural or cultural resources.
- 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_69f76df743c48190aecb6dd79efb0d95 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f795bd7d40819087be4fe0e15a5ed3 |
completed | May 3, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:04 p.m.