Triple
T18119395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valley of Elah battle of David and Goliath |
E433692
|
entity |
| Predicate | featuresArmor |
P32307
|
FINISHED |
| Object | Goliath's armor |
—
|
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: Goliath's armor | Statement: [Valley of Elah battle of David and Goliath, featuresArmor, Goliath's armor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresArmor Context triple: [Valley of Elah battle of David and Goliath, featuresArmor, Goliath's armor]
-
A.
armorFeature
chosen
Indicates that one entity is a functional or descriptive feature of another entity’s armor.
-
B.
armorType
Indicates the specific category or classification of protective armor associated with an entity.
-
C.
armour
Indicates that an entity provides protective covering or defense for another entity.
-
D.
designedArmor
Indicates that one entity created or planned the armor used or worn by another entity.
-
E.
notableArmor
Indicates that an entity is recognized for possessing or being associated with armor of particular significance, prominence, or distinction.
- 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.