Triple
T1766423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Backe Plan |
E38772
|
entity |
| Predicate | timeOfFormulation |
P13128
|
FINISHED |
| Object | early 1941 |
—
|
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: early 1941 | Statement: [Backe Plan, timeOfFormulation, early 1941]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfFormulation Context triple: [Backe Plan, timeOfFormulation, early 1941]
-
A.
timeOfCodification
Indicates the specific point in time at which something (such as a rule, law, or concept) was formally codified or recorded.
-
B.
formulatedInYear
chosen
Indicates the specific calendar year in which something was originally created, devised, or formally established.
-
C.
formalizedAt
Indicates the point in time or event at which something is officially established, documented, or given formal status.
-
D.
oftenFormulatedOn
Indicates that something (such as a statement, plan, or decision) is frequently based on, derived from, or constructed using another thing as its foundation or starting point.
-
E.
formedAt
Indicates the time or date at which an entity was created, established, or came into existence.
- 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_69a8862d562481908d7025a1c1f67c0d |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab39fc2c448190bfaf1ee8d474632a |
completed | March 6, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69aa61cbb1288190a7ba38b61905f578 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.