Triple
T32292135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bevin Plan |
E824990
|
entity |
| Predicate | proposedInPeriod |
P9416
|
FINISHED |
| Object | post–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: post–World War II | Statement: [Bevin Plan, proposedInPeriod, post–World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposedInPeriod Context triple: [Bevin Plan, proposedInPeriod, post–World War II]
-
A.
proposedInMonth
Indicates that an entity (such as a proposal or plan) was formally proposed during a specific calendar month.
-
B.
timePeriodProposed
chosen
Indicates that a specific time period has been suggested or put forward for consideration or adoption.
-
C.
appliedDuringPeriod
Indicates that an action, condition, or status was in effect throughout a specified time period.
-
D.
acquiredInPeriod
Indicates that one entity was acquired by another within a specified time period.
-
E.
proposedInYear
Indicates that something, such as a plan, idea, or piece of legislation, was formally put forward or suggested in a specific calendar year.
- 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_69f349101b788190b4f14884dc7d1ed2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: May 1, 2026, 12:44 a.m.