Triple
T28359193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danubian front of the Crimean War |
E718315
|
entity |
| Predicate | theatreShiftedTo |
P33209
|
FINISHED |
| Object | Crimea |
—
|
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: Crimea | Statement: [Danubian front of the Crimean War, theatreShiftedTo, Crimea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: theatreShiftedTo Context triple: [Danubian front of the Crimean War, theatreShiftedTo, Crimea]
-
A.
theatreOf
chosen
Indicates that an event, action, or operation takes place within or is primarily associated with a particular theatre or venue.
-
B.
transferredToTheatre
Indicates that an entity has been moved or reassigned from its previous location or status into a theatre (such as an operating theatre or performance venue).
-
C.
implementedInTheatre
Indicates that an event, work, or action is carried out, performed, or realized within a theatre setting.
-
D.
theatreOpened
Indicates that a theatre began operating or was officially opened at a particular time or event.
-
E.
theaterDirection
Indicates that one entity directs or oversees the staging and artistic execution of a theatrical production involving 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_69eff6ed5af48190be4e0adf298223e0 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64c3048248190b55266211394ecb7 |
completed | May 2, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 12:51 a.m.