Triple
T25580384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peking Plan |
E641223
|
entity |
| Predicate | implementedBefore |
P113783
|
FINISHED |
| Object | outbreak of World War II in Europe |
—
|
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: outbreak of World War II in Europe | Statement: [Peking Plan, implementedBefore, outbreak of World War II in Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: implementedBefore Context triple: [Peking Plan, implementedBefore, outbreak of World War II in Europe]
-
A.
implementedAfter
Indicates that one implementation occurs or is introduced only after another specified implementation has taken place or been completed.
-
B.
invokedBefore
Indicates that one event, action, or process is initiated or executed earlier in time than another specified event, action, or process.
-
C.
appliedBefore
chosen
Indicates that one action, process, or condition was applied earlier in time than another.
-
D.
introducedBefore
Indicates that one entity was introduced or presented earlier in time than another entity.
-
E.
controlledBefore
Indicates that one entity had control or authority over another entity during a time period that occurred earlier than a specified reference time or 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_69e75dc42b588190a98b58e0df359674 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f93364308190bcffdb00ee0ec6c7 |
completed | May 2, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 4:11 p.m.