Triple
T32292134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bevin Plan |
E824990
|
entity |
| Predicate | proposedByPosition |
P69084
|
FINISHED |
| Object | British Foreign Secretary |
—
|
NE NERFINISHED |
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: British Foreign Secretary | Statement: [Bevin Plan, proposedByPosition, British Foreign Secretary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposedByPosition Context triple: [Bevin Plan, proposedByPosition, British Foreign Secretary]
-
A.
wereProposedBy
chosen
Indicates that one or more entities (such as ideas, plans, or items) were put forward or suggested by a specific agent or source.
-
B.
coProposedBy
Indicates that a proposal, idea, or item is jointly put forward or suggested by multiple entities together.
-
C.
proposedByBody
Indicates that something (such as a decision, measure, or action) has been formally put forward or initiated by a specific governing or organizational body.
-
D.
fineProposedBy
Indicates that a specific fine has been suggested or put forward by a particular agent or authority.
-
E.
establishedByPosition
Indicates that a relationship or status is created or determined based on an entity’s role, rank, or positional placement within a structure or system.
- 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_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: May 1, 2026, 12:44 a.m.