Triple
T19674177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Israelite army |
E472409
|
entity |
| Predicate | winsBattle |
P34090
|
FINISHED |
| Object | battle against Philistines at Valley of Elah |
—
|
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: battle against Philistines at Valley of Elah | Statement: [Israelite army, winsBattle, battle against Philistines at Valley of Elah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: winsBattle Context triple: [Israelite army, winsBattle, battle against Philistines at Valley of Elah]
-
A.
winsDefinition
Indicates that one entity achieves victory or success over another in a contest, competition, or conflict.
-
B.
wonAt
Indicates that one entity achieved victory or success in a specific event, competition, or context.
-
C.
winsFor
Indicates that one entity achieves victory or success on behalf of, or in favor of, another entity.
-
D.
wonAgainst
chosen
Indicates that one entity achieved victory over another in a competition, conflict, or contest.
-
E.
victoryIn
Indicates that one entity achieves a win or success in a specific contest, event, or competitive context involving 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_69d8e514f2e08190ba70a4449519d218 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6416e19d881909248c4f778f7147a |
completed | April 20, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69e514eb37b8819091502cc954f70eba |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:45 p.m.