Triple
T35811126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jáchymov uranium mines |
E1035231
|
entity |
| Predicate | periodOfIntensiveOperation |
P97447
|
FINISHED |
| Object | Cold 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: Cold War | Statement: [Jáchymov uranium mines, periodOfIntensiveOperation, Cold War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: periodOfIntensiveOperation Context triple: [Jáchymov uranium mines, periodOfIntensiveOperation, Cold War]
-
A.
inOperationDuring
Indicates that an entity is actively functioning or in use throughout a specified time period or event.
-
B.
eraOfOperation
Indicates the time period or span of years during which an entity was active or in operation.
-
C.
operatedDuring
Indicates that an action, process, or system was functioning or in operation throughout a specified time period or event.
-
D.
partOfWorkPeriod
Indicates that a specific time span is contained within, and belongs to, a larger defined work period.
-
E.
eraOfMajorOperation
chosen
Indicates the historical period during which a major operation primarily took place or was most active.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:06 p.m.