Triple
T22712157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hess Rise |
E561629
|
entity |
| Predicate | plateMotionIndicator |
P2050
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Hess Rise, plateMotionIndicator, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plateMotionIndicator Context triple: [Hess Rise, plateMotionIndicator, yes]
-
A.
barIndication
Indicates a visual or symbolic bar used to represent, highlight, or measure a particular state, value, or condition in a context.
-
B.
plateMotion
chosen
Indicates the movement or displacement of a tectonic plate relative to other plates or a reference frame.
-
C.
usesIndicator
Indicates that one entity employs or relies on another entity as an indicator, signal, or metric for assessment, decision-making, or interpretation.
-
D.
plate3
Indicates that one entity is a third plate or dish associated with, supporting, or serving another entity in a given context.
-
E.
plateInterface
Indicates a physical or functional contact surface where one plate meets or connects with another component or plate.
- 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_69e2454f1348819088d83f420925a5c1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1790998fc8190962e21a28dd08d29 |
completed | April 29, 2026, 3:20 a.m. |
| PD | Predicate disambiguation | batch_69ee62bd657c81909f7b01245b080a5f |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:18 p.m.