Triple
T35089691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Siple |
E1012682
|
entity |
| Predicate | hasSatelliteCone |
P70757
|
FINISHED |
| Object | The Blob |
—
|
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: The Blob | Statement: [Mount Siple, hasSatelliteCone, The Blob]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSatelliteCone Context triple: [Mount Siple, hasSatelliteCone, The Blob]
-
A.
hasSatelliteCones
chosen
Indicates that an entity (typically a volcano) possesses one or more smaller subsidiary cones located on or around its main structure.
-
B.
hasCone
Indicates that one entity possesses, is equipped with, or is characterized by a cone or cone-shaped component.
-
C.
hasMultipleCones
Indicates that an entity is associated with more than one cone-shaped object or structure.
-
D.
hasConeType
Indicates that an entity possesses or is associated with a specific type or category of cone.
-
E.
hasEndCones
Indicates that an object possesses cone-shaped elements at one or both of its ends.
- 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_69f76dd432ec8190969bc32acfc152b1 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:01 p.m.