Triple
T18119182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elah Valley |
E433687
|
entity |
| Predicate | biblicalEventLocation |
P127335
|
FINISHED |
| Object | battle between Israelites and Philistines |
—
|
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 between Israelites and Philistines | Statement: [Elah Valley, biblicalEventLocation, battle between Israelites and Philistines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: biblicalEventLocation Context triple: [Elah Valley, biblicalEventLocation, battle between Israelites and Philistines]
-
A.
associatedBiblicalEvent
Indicates that there is a connection or linkage between an entity and a specific event described in the Bible.
-
B.
scripturalEvent
Indicates that an event is described, referenced, or established within a scriptural or sacred text.
-
C.
biblicalCityName
Indicates that the entity is identified by a name used for a city in the Bible.
-
D.
significantEventPlace
chosen
Indicates the place where a significant event occurred or is associated with an entity.
-
E.
revelationPlace
Indicates the place or location where a revelation, disclosure, or revealing event occurs.
- 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_69d8b909e8cc81908df4cc2b8ea6d11f |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddd843e88190abbc173dbc9b450a |
completed | April 19, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_69e43313ca788190baa224269e71de49 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:28 a.m.