Triple
T33859009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bulusan |
E867869
|
entity |
| Predicate | hasVolcanicOriginLandforms |
P178826
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Bulusan, hasVolcanicOriginLandforms, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVolcanicOriginLandforms Context triple: [Bulusan, hasVolcanicOriginLandforms, true]
-
A.
volcanicOrigin
Indicates that something originates from, is produced by, or is directly associated with volcanic activity or processes.
-
B.
hasVolcanicLandform
chosen
Indicates that one entity possesses, contains, or is characterized by a volcanic landform (such as a volcano, caldera, or lava plateau).
-
C.
foundedAsVolcanoes
Indicates that one entity was originally established or came into existence as a volcano or group of volcanoes.
-
D.
hasLandformOrigin
Indicates that something originates from, or is formed by, a particular landform.
-
E.
isVolcanic
Indicates that something is characterized by or related to volcanic activity, such as originating from, produced by, or associated with a volcano.
- 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_69f349943ccc8190a3c41a3e0ae46cbf |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: May 1, 2026, 1:47 a.m.