Triple
T32919412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Sea Shipyard |
E842103
|
entity |
| Predicate | historicalEraOfMajorActivity |
P18555
|
FINISHED |
| Object | Soviet era |
—
|
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: Soviet era | Statement: [Black Sea Shipyard, historicalEraOfMajorActivity, Soviet era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalEraOfMajorActivity Context triple: [Black Sea Shipyard, historicalEraOfMajorActivity, Soviet era]
-
A.
historicalPeriodOfMajorActivity
chosen
Indicates the historical period during which an entity carried out its most significant or influential activities.
-
B.
historicalEraOfSuccess
Indicates that an entity achieved notable success or prominence during a specified historical era.
-
C.
historicalPeriodOfSignificance
Indicates the time period during which an entity is considered to have had its most important or influential historical impact.
-
D.
historicalPeriodOfGreatestUse
Indicates the time period during which something was used most intensively or prevalently.
-
E.
historicalEraUsheredIn
Indicates the historical era or period that was initiated or brought about as a result of a particular event, action, or 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_69f3494779388190a5d3e97f92278be2 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ffbf84f4948190b41a7bba07ae61ec |
completed | May 9, 2026, 11:13 p.m. |
| PD | Predicate disambiguation | batch_69ffbf0a59f88190870dbe25d8a63a00 |
completed | May 9, 2026, 11:11 p.m. |
Created at: May 1, 2026, 1:19 a.m.