Triple
T33858959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irosin |
E867868
|
entity |
| Predicate | isInGeologicRegion |
P42212
|
FINISHED |
| Object | Bicol volcanic arc |
—
|
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: Bicol volcanic arc | Statement: [Irosin, isInGeologicRegion, Bicol volcanic arc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInGeologicRegion Context triple: [Irosin, isInGeologicRegion, Bicol volcanic arc]
-
A.
hasGeologicalProvince
Indicates that a geographic area or location is associated with, or belongs to, a specific geological province characterized by common geological features or history.
-
B.
regionalGeologyContext
Indicates the broader geological setting or framework within which a specific geological feature, event, or observation occurs.
-
C.
geologicalProvinceOf
chosen
Indicates that one entity is the geological province to which another entity (such as a region or feature) belongs or is classified.
-
D.
geologicalAffinity
Indicates a relationship where entities share similar or related geological characteristics, origins, or formations.
-
E.
geologicalOriginRegion
Indicates the geographic region from which a geological feature, material, or formation originally derives.
- 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_69f7007a313481909f162daeffb26b8e |
completed | May 3, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:47 a.m.