Triple
T9896007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Elchingen |
E182173
|
entity |
| Predicate | tookPlaceOnStructure |
P37991
|
FINISHED |
| Object | bridge at Elchingen |
—
|
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 at Elchingen | Statement: [Battle of Elchingen, tookPlaceOnStructure, bridge at Elchingen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tookPlaceOnStructure Context triple: [Battle of Elchingen, tookPlaceOnStructure, bridge at Elchingen]
-
A.
tookPlaceInBuilding
chosen
Indicates that an event or action occurred within the physical premises of a specific building.
-
B.
buildingIncorporatedInto
Indicates that one building has been structurally or functionally integrated into another building as part of a combined or expanded construction.
-
C.
locationOfStructure
Indicates that a particular structure is situated at or occupies a specific location.
-
D.
towerAttachment
Indicates that one entity is physically attached to or structurally connected with a tower.
-
E.
builtStructureFor
Indicates that one entity constructed or assembled a structure specifically intended for the use, benefit, or purpose of another 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_69ca82876f8081909cf75df0f99bb13f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb4a9d2f4819086cfdd42b613cd8c |
completed | April 2, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69cd1d872d50819096b7ab166a8decf1 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:39 p.m.