Triple
T37664830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basalt Deltas |
E937797
|
entity |
| Predicate | hasTerrainBlock |
P189727
|
FINISHED |
| Object | basalt |
—
|
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: basalt | Statement: [Basalt Deltas, hasTerrainBlock, basalt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTerrainBlock Context triple: [Basalt Deltas, hasTerrainBlock, basalt]
-
A.
hasTerrainFor
Indicates that a location or area possesses terrain suitable or designated for a particular use, activity, or feature.
-
B.
hasTerrainCharacter
Indicates that one entity possesses or exhibits a particular terrain-related feature or characteristic in relation to another entity.
-
C.
hasIntermediateTerrain
Indicates that something is situated on or characterized by terrain of medium or moderate difficulty or ruggedness, between easy/flat and difficult/extreme terrain.
-
D.
hasNoTerrainType
Indicates that an entity explicitly lacks any associated terrain type within the modeled relationship or context.
-
E.
hasGeneralTerrain
chosen
Indicates that an entity is characterized by or associated with a particular overall type of terrain.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69feba0f09508190b3e871c62b19ec7f |
completed | May 9, 2026, 4:37 a.m. |
| PD | Predicate disambiguation | batch_69feb957fe7c8190969fb31a6d1a59c8 |
completed | May 9, 2026, 4:34 a.m. |
Created at: May 3, 2026, 4:18 p.m.