Triple
T20273747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vøring Margin |
E502956
|
entity |
| Predicate | hasPostRiftProcess |
P1410
|
FINISHED |
| Object | thermal subsidence |
—
|
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: thermal subsidence | Statement: [Vøring Margin, hasPostRiftProcess, thermal subsidence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPostRiftProcess Context triple: [Vøring Margin, hasPostRiftProcess, thermal subsidence]
-
A.
hasProcess
chosen
Indicates that an entity is associated with, participates in, or is characterized by a particular process.
-
B.
hasPosteriorRegion
Indicates that one entity constitutes or occupies the rear or back (posterior) region of another entity.
-
C.
hasPostscript
Indicates that something includes an additional note or message appended after its main content.
-
D.
hasCutAfterRound
Indicates that an entity is eliminated or removed from participation after a specified round.
-
E.
hasReprocessingActivity
Indicates that an entity engages in or is associated with an activity that reprocesses materials, resources, or products.
- 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_69e0b4b0e79c8190bd61f22ef1329fa8 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e675e104f081909d17c1963a5db528 |
completed | April 20, 2026, 6:52 p.m. |
| PD | Predicate disambiguation | batch_69e55b1e5e1c8190ba8a5544b1db9e1d |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 10:28 a.m.