Triple
T9103582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Lodi |
E218418
|
entity |
| Predicate | mainBridge |
P36619
|
FINISHED |
| Object | bridge over the Adda at Lodi |
—
|
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: bridge over the Adda at Lodi | Statement: [Battle of Lodi, mainBridge, bridge over the Adda at Lodi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainBridge Context triple: [Battle of Lodi, mainBridge, bridge over the Adda at Lodi]
-
A.
otherMainBridge
Indicates that one bridge serves as an alternative or secondary primary bridge in relation to another main bridge.
-
B.
hasBridgeTo
chosen
Indicates that one entity is connected to another by a bridge or bridging structure that allows passage or linkage between them.
-
C.
mainMediator
Indicates that an entity serves as the primary intermediary or facilitator through which interaction, communication, or influence between other entities is conducted.
-
D.
mainBase
Indicates that one entity serves as the primary or central base or headquarters for another entity.
-
E.
bridgeName
Indicates the designated name assigned to a specific bridge.
- 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_69ca83db7448819090d0a5de842ef2ac |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca56f1f10819091abadf7cd06c3a6 |
completed | April 1, 2026, 4:56 a.m. |
| PD | Predicate disambiguation | batch_69cc65fc7f408190a5846e29ab3b97e5 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:15 p.m.