Triple
T38222006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | גָּלְיָת |
E1012035
|
entity |
| Predicate | נלחם נגד |
P174097
|
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.
armedAgainst
Indicates that one entity is equipped with weapons or defensive capabilities specifically in preparation for potential conflict with another entity.
-
B.
combatedBy
chosen
Indicates that an entity is opposed, fought against, or countered by another entity.
-
C.
struggleFor
Indicates a relationship where one entity exerts effort or engages in conflict in order to obtain, achieve, or defend another entity or goal.
-
D.
engagesInCyclicalStruggleWith
Indicates a relationship in which two entities are locked in a recurring, back-and-forth conflict or opposition that repeats over time.
-
E.
opposingForce
Indicates a relationship where one entity actively resists, counters, or works against the actions, goals, or influence of another 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_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.