Triple
T17089162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volcán San Miguel |
E414677
|
entity |
| Predicate | hasSecondaryFeature |
P90082
|
FINISHED |
| Object | flank vents (historically reported) |
—
|
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: flank vents (historically reported) | Statement: [Volcán San Miguel, hasSecondaryFeature, flank vents (historically reported)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondaryFeature Context triple: [Volcán San Miguel, hasSecondaryFeature, flank vents (historically reported)]
-
A.
hasSecondary
chosen
Indicates that an entity is associated with an additional or subordinate counterpart beyond its primary one.
-
B.
hasSecondaryUsage
Indicates that an entity is associated with an additional, non-primary function or purpose beyond its main intended use.
-
C.
hasSecondaryBase
Indicates that an entity possesses or is associated with a secondary or additional base, distinct from its primary base.
-
D.
hasPrimaryFeature
Indicates that an entity possesses a main or most characteristic feature that defines or distinguishes it.
-
E.
hasSecondaryCore
Indicates that an entity possesses an additional, subordinate core component alongside its primary core.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbe9dc808190ab20537100e7ddee |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d67b14481909fcdbdeaa5c34785 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.