Triple
T36690479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yahad (Israel) |
E905940
|
entity |
| Predicate | foundedAfterSplitFrom |
P29282
|
FINISHED |
| Object | Likud |
—
|
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: Likud | Statement: [Yahad (Israel), foundedAfterSplitFrom, Likud]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAfterSplitFrom Context triple: [Yahad (Israel), foundedAfterSplitFrom, Likud]
-
A.
wasDividedFrom
Indicates that one entity was separated or split off from another entity, resulting in two distinct parts or groups.
-
B.
wasDividedFromYear
Indicates that an entity began to be separated or partitioned starting from a specified year.
-
C.
laterRefoundedAs
Indicates that an entity was dissolved or ceased to exist and was subsequently re-established under a new or modified form, identity, or organization.
-
D.
foundedAfterDestructionOf
Indicates that one entity was founded only after the destruction or demise of another entity.
-
E.
foundedFrom
chosen
Indicates that an entity was established or originated starting from a particular source, place, or prior entity.
- 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_69f76e70d2448190bdd3ce781ba971c5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff289541e0819096eeceb8e6332650 |
completed | May 9, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69ff281ab1988190920f0443be9f10cc |
completed | May 9, 2026, 12:27 p.m. |
Created at: May 3, 2026, 4:12 p.m.