Triple
T24462448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Amvrakia |
E616864
|
entity |
| Predicate | hasRegionFeature |
P151519
|
FINISHED |
| Object | mountainous surroundings |
—
|
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: mountainous surroundings | Statement: [Lake Amvrakia, hasRegionFeature, mountainous surroundings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionFeature Context triple: [Lake Amvrakia, hasRegionFeature, mountainous surroundings]
-
A.
associatedRegionFeature
chosen
Indicates that something is linked or connected to a particular geographic or regional feature.
-
B.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
C.
hasRegionFunction
Indicates that a region is associated with a particular function, role, or operational purpose.
-
D.
hasRegionProperty
Indicates that a region is associated with a specific property or characteristic.
-
E.
hasBaseRegion
Indicates that one entity is situated upon, supported by, or primarily associated with a specific underlying region or area.
- 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_69e2d7ef9fe08190a0613908758b4e86 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f298cb4cb4819095d26cdd98a7a570 |
completed | April 29, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:19 a.m.