Triple
T33963347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lourmel |
E870780
|
entity |
| Predicate | isOnSideOfRiver |
P95833
|
FINISHED |
| Object | Left Bank |
—
|
NE NERFINISHED |
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: Left Bank | Statement: [Lourmel, isOnSideOfRiver, Left Bank]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnSideOfRiver Context triple: [Lourmel, isOnSideOfRiver, Left Bank]
-
A.
isOnBorderRiver
Indicates that something is located along or directly adjacent to a river that forms a border between areas.
-
B.
isOnLeftBank
chosen
Indicates that one entity is located on the left bank (left side) of a river or similar waterway relative to its flow direction.
-
C.
isOnRiverIsland
Indicates that one entity (typically a place or structure) is located on an island situated within a river.
-
D.
locatedAcrossRiverFrom
Indicates that one entity is situated on the opposite side of a river relative to another entity.
-
E.
locatedInRiverArea
Indicates that one entity is situated within the geographic area occupied by, adjacent to, or directly associated with a particular river.
- 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_69f3499ce8e88190b66e1d49ad8c7037 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:50 a.m.