Triple
T28359192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danubian front of the Crimean War |
E718315
|
entity |
| Predicate | earlyPhaseOf |
P63407
|
FINISHED |
| Object | Crimean War |
—
|
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: Crimean War | Statement: [Danubian front of the Crimean War, earlyPhaseOf, Crimean War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlyPhaseOf Context triple: [Danubian front of the Crimean War, earlyPhaseOf, Crimean War]
-
A.
earlyPhase
chosen
Indicates that the related process, project, or development is in its initial or beginning stage.
-
B.
earlyStrategy
Indicates that an entity adopts or implements a strategy at an early stage or time relative to a process, event, or development.
-
C.
firstPhaseStart
Indicates the point in time when the initial phase of a process or sequence begins.
-
D.
earlyUse
Indicates that an entity is used or adopted at an unusually early time or stage relative to a typical or expected point of use.
-
E.
earlyTraining
Indicates that an entity receives or provides training at an early stage relative to a process, development period, or typical timeline.
- 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_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 12:51 a.m.