Triple
T36044709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soputan volcanic complex |
E1042635
|
entity |
| Predicate | primaryEdifice |
P127516
|
FINISHED |
| Object | Mount Soputan |
E320097
|
NE 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: Mount Soputan | Statement: [Soputan volcanic complex, primaryEdifice, Mount Soputan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryEdifice Context triple: [Soputan volcanic complex, primaryEdifice, Mount Soputan]
-
A.
hasMainEdifice
chosen
Indicates that an entity possesses or is associated with a primary or principal building or structure.
-
B.
publicBuilding
Indicates that a building is designated for public use or access, typically serving communal, governmental, or civic functions.
-
C.
isMainBuildingOf
Indicates that a building serves as the primary or central facility associated with a particular organization, complex, or site.
-
D.
primaryArchitecture
Indicates that one entity serves as the main or predominant architectural style, structure, or design associated with another entity.
-
E.
foundingBuilding
Indicates that a particular building is the original or primary structure where an organization, institution, or entity was founded.
- F. None of above.
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_69f76e2e41f8819091f9fb0536920fec |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39a30666e08190b49fda5e72180700 |
completed | June 22, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:07 p.m.