Triple
T17074804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fordow enrichment facility |
E414320
|
entity |
| Predicate | publicRevelationDate |
P26941
|
FINISHED |
| Object | 2009 |
—
|
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: 2009 | Statement: [Fordow enrichment facility, publicRevelationDate, 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicRevelationDate Context triple: [Fordow enrichment facility, publicRevelationDate, 2009]
-
A.
timeOfFirstRevelation
chosen
Indicates the specific time at which the first revelation or initial disclosure of something occurred.
-
B.
reunveiledOn
Indicates that something was revealed or made publicly known again on a specific date or occasion.
-
C.
hasRevelationPeriod
Indicates the time span or phase during which a revelation, disclosure, or unveiling of something occurs or is valid.
-
D.
revealedAfter
Indicates that one piece of information, event, or state becomes known or disclosed only subsequent to another specified point in time or condition.
-
E.
occasionOfRevelation
Indicates the specific event, situation, or context during which a revelation or disclosure took place.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbc3b69c819093b32da3998eed46 |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d642f74819098c014135e249b27 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:34 a.m.