Triple
T37371891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | חלוצה |
E927864
|
entity |
| Predicate | includedTogetherWith |
P137318
|
FINISHED |
| Object | עבדת |
—
|
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: עבדת | Statement: [חלוצה, includedTogetherWith, עבדת]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedTogetherWith Context triple: [חלוצה, includedTogetherWith, עבדת]
-
A.
includedWith
Indicates that one entity is provided or packaged together as part of another entity.
-
B.
actedTogetherWith
chosen
Indicates that two entities participated in the same performance or production, collaborating or appearing together in an acting context.
-
C.
interpretedTogetherWith
Indicates that one entity is understood, analyzed, or explained in conjunction with another, with their meanings or interpretations considered jointly rather than separately.
-
D.
heldTogetherWith
Indicates that two or more entities are physically joined or kept in contact by some binding, fastening, or cohesive force.
-
E.
includedSingle
Indicates that one specific, individual item is contained within or made part of another set, group, or collection.
- 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_69f76eb820248190a5c395ca50ad002a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.