Triple
T22843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potsdam Conference |
E453
|
entity |
| Predicate | tookPlaceDuring |
P1127
|
FINISHED |
| Object | final months of World War II |
—
|
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: final months of World War II | Statement: [Potsdam Conference, tookPlaceDuring, final months of World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tookPlaceDuring Context triple: [Potsdam Conference, tookPlaceDuring, final months of World War II]
-
A.
enactedDuring
chosen
Indicates that an action, event, or state occurred within the temporal span of a specified time period or event.
-
B.
operatedDuring
Indicates that an action, process, or system was functioning or in operation throughout a specified time period or event.
-
C.
wasDevelopedInPeriod
Indicates that something was created, produced, or brought into existence during a specified time period.
-
D.
servedAsPresidentDuring
Indicates that a person held the office of president for the duration of a specified time period or event.
-
E.
writtenDuring
Indicates that the creation or authorship of something took place within a specified time period or historical event.
- 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_69a243b4ac2c8190b93c303df797b7b2 |
completed | Feb. 28, 2026, 1:24 a.m. |
| NER | Named-entity recognition | batch_69a246e94ca881908f7a7d2c0b293033 |
completed | Feb. 28, 2026, 1:37 a.m. |
| PD | Predicate disambiguation | batch_69a24654724481909ba14b7f68d2a472 |
completed | Feb. 28, 2026, 1:35 a.m. |
Created at: Feb. 28, 2026, 1:34 a.m.