Triple
T30874334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Scutari |
E786432
|
entity |
| Predicate | riverOrStraitNearby |
P8567
|
FINISHED |
| Object | Bosporus |
—
|
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: Bosporus | Statement: [Battle of Scutari, riverOrStraitNearby, Bosporus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverOrStraitNearby Context triple: [Battle of Scutari, riverOrStraitNearby, Bosporus]
-
A.
nearbyStrait
Indicates that one entity is located close to or adjacent to a particular strait.
-
B.
nearbyWatercourse
chosen
Indicates that one entity is located close to or alongside a natural or artificial watercourse, such as a river, stream, or canal.
-
C.
riverLocation
Indicates that a river is located in, passes through, or is geographically associated with a specified place or region.
-
D.
nearbyRiverProject
Indicates that there is a project located close to or associated with a nearby river.
-
E.
nearestLargeBodyOfWater
Indicates the closest significant body of water in proximity to a given location or 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 29, 2026, 8:48 p.m.