Triple
T11789060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HaPoel HaMizrachi |
E280343
|
entity |
| Predicate | combined |
P70673
|
FINISHED |
| Object | trade union activity and religious values |
—
|
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: trade union activity and religious values | Statement: [HaPoel HaMizrachi, combined, trade union activity and religious values]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combined Context triple: [HaPoel HaMizrachi, combined, trade union activity and religious values]
-
A.
combinedIn
chosen
Indicates that two or more entities are merged, joined, or used together to form a single combined whole or context.
-
B.
composedIn
Indicates that a creative work was written or musically composed within a particular place or during a specific time period.
-
C.
combinedConstruction
Indicates that multiple construction elements, processes, or projects are joined or executed together as a single combined construction activity.
-
D.
composedTo
Indicates that one entity created or authored another entity, typically a work such as a piece of music, writing, or art.
-
E.
committed
Indicates that an agent has carried out or been responsible for a specific act, event, or wrongdoing.
- 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a587c2d881909297c3a6c7d26080 |
completed | April 10, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69d8a2491f048190853239bc05090bf4 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.