Triple
T3696413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shira |
E78469
|
entity |
| Predicate | isErodedRemnantOf |
P38602
|
FINISHED |
| Object | ancient volcanic cone |
—
|
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: ancient volcanic cone | Statement: [Shira, isErodedRemnantOf, ancient volcanic cone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isErodedRemnantOf Context triple: [Shira, isErodedRemnantOf, ancient volcanic cone]
-
A.
isYoungerRemnantOf
Indicates that one entity is the surviving, younger portion or successor of another entity that existed earlier and has largely disappeared or transformed.
-
B.
hasErosionFeature
chosen
Indicates that one entity exhibits or contains a specific erosion-related feature or form resulting from erosional processes.
-
C.
remnants
Indicates that parts or traces of something remain after the main portion has been removed, used, or destroyed.
-
D.
lastRemnantOf
Indicates that one entity is the sole remaining instance or surviving part of another entity, after all similar or related instances have disappeared.
-
E.
hasCauseOfDestruction
Indicates that one entity is the cause or agent responsible for the destruction or damage of another entity.
- 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_69ad85e3b1888190abc983e06968696d |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc50f9ad88190a926042fa73d65dc |
completed | March 8, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69adb84dc5808190850aa6975cb09e27 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:26 p.m.