Triple
T15316483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sevastopol Bay |
E366171
|
entity |
| Predicate | strategicSince |
P118083
|
FINISHED |
| Object | 18th century |
—
|
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: 18th century | Statement: [Sevastopol Bay, strategicSince, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strategicSince Context triple: [Sevastopol Bay, strategicSince, 18th century]
-
A.
strategicStatus
Indicates the strategic condition or importance of an entity within a broader plan, context, or objective.
-
B.
strategicReason
Indicates that one entity serves as a reason, justification, or motivation for another entity’s strategic decision, plan, or action.
-
C.
strategicStance
Indicates the overarching strategic position, approach, or orientation an entity adopts in relation to others or to a particular situation.
-
D.
hasStrategicContext
Indicates that something is associated with or situated within a broader strategic framework, plan, or set of objectives.
-
E.
strategizesFor
Indicates that one entity plans or devises strategies on behalf of, or in support of, another entity.
- F. None of above. chosen
Provenance (4 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_69d85a121520819093dcce999fdefe1a |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03dd1d384819098f38402a8740d91 |
completed | April 16, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_69deca935e2c8190b640987ddfc542b9 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2e413481909d9180a8d78d2c17 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:16 a.m.