Triple
T15079229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bonneval |
E380090
|
entity |
| Predicate | riverCrossingFeature |
P104419
|
FINISHED |
| Object | stone bridges |
—
|
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: stone bridges | Statement: [Bonneval, riverCrossingFeature, stone bridges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverCrossingFeature Context triple: [Bonneval, riverCrossingFeature, stone bridges]
-
A.
riverCrossingStructure
Indicates a structure that allows passage across a river, such as by spanning or traversing it.
-
B.
riverFeatureType
Indicates the specific kind or category of physical or functional feature associated with a river (e.g., source, mouth, tributary, channel segment).
-
C.
hasRiverCrossingType
chosen
Indicates the type or nature of a river crossing associated with an entity (e.g., bridge, ford, ferry).
-
D.
crossedByRiver
Indicates that a river passes across or through a specified area, feature, or route.
-
E.
waterwayTypeCrossed
Indicates the specific kind of waterway (e.g., river, canal, stream) that is being crossed in the described relationship or action.
- 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_69d85cd7683881908d405c1b5d7b4f7f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69dff80008c88190840f94222f867478 |
completed | April 15, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69deb9645b9c8190a5712456dbd78029 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:03 a.m.