Triple
T38548629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King George VI Reservoir |
E925041
|
entity |
| Predicate | embankmentType |
P103573
|
FINISHED |
| Object | earth embankment |
—
|
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: earth embankment | Statement: [King George VI Reservoir, embankmentType, earth embankment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: embankmentType Context triple: [King George VI Reservoir, embankmentType, earth embankment]
-
A.
hasEmbankment
Indicates that one entity possesses or is characterized by an embankment, such as a raised structure built to contain, support, or protect against water or terrain.
-
B.
hasEmbankmentMaterial
chosen
Indicates that an embankment is composed of, or constructed using, a specified material.
-
C.
isOnEmbankment
Indicates that one entity is located on or along the raised bank or levee structure associated with a body of water or roadway.
-
D.
berthType
Indicates the specific kind or category of berth associated with an entity, such as the type of sleeping or docking space provided.
-
E.
bayType
Indicates the specific kind or classification of a bay associated with an entity.
- 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_69f76eaeb69c8190b367df9330d6f6af |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcd31521d48190adb9cbcaf4a92275 |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f81cbc8190b4fd3bfc3106c1f3 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:32 p.m.