Triple
T9661400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Early Bronze Age |
E233596
|
entity |
| Predicate | conflictAndWarfare |
P12
|
FINISHED |
| Object | use of bronze weapons |
—
|
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: use of bronze weapons | Statement: [Early Bronze Age, conflictAndWarfare, use of bronze weapons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictAndWarfare Context triple: [Early Bronze Age, conflictAndWarfare, use of bronze weapons]
-
A.
militaryConflict
chosen
Indicates a relationship where two or more parties are engaged in organized, armed hostilities or warfare against each other.
-
B.
politicalConflict
Indicates a relationship where entities are engaged in opposing political positions, struggles, or disputes, often involving competition for power, influence, or policy outcomes.
-
C.
conflictCountry
Indicates that there is an armed conflict or war involving the referenced country as a participant.
-
D.
militaryConflictIn
Indicates that a military conflict takes place within, or is geographically located in, a specified area or region.
-
E.
regionOfConflict
Indicates that a specified region is the location where a particular conflict or dispute takes place.
- 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_69ca848d3b6c8190ae98ea554dea58df |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c0a15e4819092ea0fb2cb6e1c12 |
completed | April 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b3239c8190b3ae3b9bd121e4bd |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:14 p.m.