Triple
T27201609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vienna Basin |
E683748
|
entity |
| Predicate | hasSubsurfaceStructure |
P184357
|
FINISHED |
| Object | fault-bounded blocks |
—
|
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: fault-bounded blocks | Statement: [Vienna Basin, hasSubsurfaceStructure, fault-bounded blocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubsurfaceStructure Context triple: [Vienna Basin, hasSubsurfaceStructure, fault-bounded blocks]
-
A.
isSubsurfaceStructure
Indicates that one entity is a structure located below the surface of another medium or environment.
-
B.
hasSubsurfacePlatforms
Indicates that an entity includes or is equipped with platforms located below the surface or underground.
-
C.
hasSubsurfaceLines
Indicates that an entity possesses lines or features located beneath its visible surface.
-
D.
hasBottomSubstrate
Indicates that one entity serves as the underlying or supporting substrate or base layer for another entity.
-
E.
hasSubSurfacePlatformsFor
Indicates that one entity provides or contains subsurface platforms intended to support, serve, or be used by another entity.
- F. None of above. chosen
Provenance (4 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_69eefad1fd5c8190a4a46ea6afe58bfa |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69f7b0e3917481908a394680d76743c3 |
completed | May 3, 2026, 8:32 p.m. |
Created at: April 27, 2026, 9:36 a.m.