Triple
T2728361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zionist organizations |
E60248
|
entity |
| Predicate | organize |
P123
|
FINISHED |
| Object | Zionist congresses |
—
|
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: Zionist congresses | Statement: [Zionist organizations, organize, Zionist congresses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organize Context triple: [Zionist organizations, organize, Zionist congresses]
-
A.
organizes
chosen
Indicates that one entity arranges, coordinates, or structures activities, items, or people into an ordered or planned form for a particular purpose.
-
B.
organizedAs
Indicates how elements are structured, arranged, or grouped according to a particular organizing principle or scheme.
-
C.
organizedUnder
Indicates that one entity is administratively or structurally placed within, and governed or managed by, another entity.
-
D.
organizedDuring
Indicates that an event or activity was arranged or took place within a specified time period or temporal context.
-
E.
organizedInResponseTo
Indicates that an action or event was arranged or carried out specifically as a reaction to a prior situation, event, or stimulus.
- 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_69ab4b75cd908190b691ef0d1801acda |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdaeaee388190a21e7fa0b8f83546 |
completed | March 7, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69abd82586f88190a98f60d3247fe2d3 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.