Triple
T24853380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sixth Zionist Congress |
E621952
|
entity |
| Predicate | consideredProposalFrom |
P69084
|
FINISHED |
| Object | British government |
—
|
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 government | Statement: [Sixth Zionist Congress, consideredProposalFrom, British government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consideredProposalFrom Context triple: [Sixth Zionist Congress, consideredProposalFrom, British government]
-
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.
hasProposal
Indicates that an entity possesses, is associated with, or is the subject of a specific proposal.
-
C.
coProposedBy
Indicates that a proposal, idea, or item is jointly put forward or suggested by multiple entities together.
-
D.
relatedProposal
Indicates that one proposal has a specified relationship or association with another proposal.
-
E.
hasProposed
Indicates that one entity has formally suggested or put forward something (such as an idea, plan, or offer) to another entity for consideration or acceptance.
- 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_69e2fac297e481909d3aedc75f585e42 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:21 a.m.