Triple
T23330150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Belgrade (1789) |
E591421
|
entity |
| Predicate | fortressInvolved |
P36422
|
FINISHED |
| Object | Belgrade fortress |
—
|
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: Belgrade fortress | Statement: [Battle of Belgrade (1789), fortressInvolved, Belgrade fortress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fortressInvolved Context triple: [Battle of Belgrade (1789), fortressInvolved, Belgrade fortress]
-
A.
fortInvolved
chosen
Indicates that a fort is involved or participates in a particular event, action, or relationship between entities.
-
B.
fortressDefended
Indicates that a fortress is actively protected against threats or attacks by some defending force.
-
C.
containsFortress
Indicates that a location or area includes a fortress within its boundaries.
-
D.
fortressLocation
Indicates that a fortress is located at or in a specified place or geographic area.
-
E.
locatedInFortress
Indicates that an entity is situated within the boundaries or interior of a fortress.
- 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_69e25d20156c81908c5c53195bd9c738 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f197ece360819099da8443dd86a355 |
completed | April 29, 2026, 5:32 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:15 p.m.