Triple
T27510543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mageik |
E694395
|
entity |
| Predicate | isRelatedToFeatureType |
P101663
|
FINISHED |
| Object | volcano |
—
|
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: volcano | Statement: [Mageik, isRelatedToFeatureType, volcano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRelatedToFeatureType Context triple: [Mageik, isRelatedToFeatureType, volcano]
-
A.
isFeatureOf
Indicates that something functions as a characteristic, attribute, or component belonging to or describing another entity.
-
B.
includesFeatureTypes
chosen
Indicates that an entity contains or encompasses specific types of features as part of its composition or definition.
-
C.
supportsRelationType
Indicates that one entity provides assistance, endorsement, or structural backing to another entity in the context of a specified relation type.
-
D.
relatedToStructureType
Indicates that one entity has an association or connection with a particular type or category of structure.
-
E.
isRelatedSymbol
Indicates that one symbol has a defined relationship or association with another symbol, such as similarity, correspondence, or functional connection.
- 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_69ef53842afc8190ba6bd4e4999bda67 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 1:15 p.m.