Triple
T38222012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | גָּלְיָת |
E1012035
|
entity |
| Predicate | הומת באמצעות |
P129262
|
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: [גָּלְיָת, הומת באמצעות, חרב של עצמו]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: הומת באמצעות Context triple: [גָּלְיָת, הומת באמצעות, חרב של עצמו]
-
A.
methodOfDeliverance
Indicates the means, process, or method by which deliverance, rescue, or liberation is achieved for an entity.
-
B.
crossedWithHelpOf
Indicates that one entity moved across or through something with assistance provided by another entity or means.
-
C.
usedVia
chosen
Indicates that an entity performs or achieves something by means of, or through the use of, another entity or mechanism.
-
D.
metThrough
Indicates that two entities became acquainted or connected as a result of an intermediary person, event, platform, or context through which they first met.
-
E.
survivingUse
Indicates that one entity continues to make use of another entity or resource after an event that could have ended or invalidated that use.
- 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_69f76dd25e0c81909f2abd0803e5e3ee |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:30 p.m.