Triple
T35505638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rabaul volcano |
E1026140
|
entity |
| Predicate | typeLocalityOf |
P35175
|
FINISHED |
| Object | Rabaul-type caldera |
—
|
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: Rabaul-type caldera | Statement: [Rabaul volcano, typeLocalityOf, Rabaul-type caldera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeLocalityOf Context triple: [Rabaul volcano, typeLocalityOf, Rabaul-type caldera]
-
A.
typeLocality
chosen
Indicates the specific geographic location where a specimen or taxon was originally found and formally described.
-
B.
typeLocalityContext
Indicates the contextual circumstances or setting (such as geographic, temporal, or environmental details) associated with the designated type locality of a specimen or taxon.
-
C.
subjectLocality
Indicates that one entity serves as the geographic or jurisdictional area associated with, relevant to, or governing the other entity.
-
D.
originLocality
Indicates the specific locality or place where an entity (typically a specimen or item) originally came from or was collected.
-
E.
containsLocality
Indicates that one place or area geographically includes or encompasses another locality within its boundaries.
- 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_69f76dfd61208190b93ec6dc439cab41 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.