Triple
T30617578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | בְּצַלְאֵל |
E779354
|
entity |
| Predicate | שותף מרכזי |
P169623
|
FINISHED |
| Object | אָהֳלִיאָב בן אחיסמך |
—
|
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: אָהֳלִיאָב בן אחיסמך | Statement: [בְּצַלְאֵל, שותף מרכזי, אָהֳלִיאָב בן אחיסמך]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: שותף מרכזי Context triple: [בְּצַלְאֵל, שותף מרכזי, אָהֳלִיאָב בן אחיסמך]
-
A.
sharedMonarchWith
Indicates that two political entities are or were ruled by the same monarch at a given time or over a specified period.
-
B.
partnerInGambling
Indicates that two or more entities participate together as partners in gambling activities or ventures.
-
C.
partnerInSeries
Indicates that two entities are co-participants or collaborators within the same series, jointly contributing to or appearing in that ongoing sequence.
-
D.
supportedSide
Indicates that one entity backed, favored, or provided assistance to a particular side or party in a conflict, dispute, or competition.
-
E.
partnerInUnionWith
Indicates a mutual partnership or union relationship between two entities, such as a civil, domestic, or similar legally or socially recognized union.
- F. None of above. chosen
Provenance (4 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_69f224a3307081909a6dca8ca75dbf48 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f689eca0348190a4f8e54e0a56f797 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f0353c88190a05b2db449abe0f4 |
completed | May 2, 2026, 10:47 p.m. |
Created at: April 29, 2026, 8:26 p.m.