Triple
T24763952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bronze |
E619527
|
entity |
| Predicate | precededMaterialInHistory |
P3444
|
FINISHED |
| Object | wrought iron for tools and 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: wrought iron for tools and weapons | Statement: [Bronze, precededMaterialInHistory, wrought iron for tools and weapons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precededMaterialInHistory Context triple: [Bronze, precededMaterialInHistory, wrought iron for tools and weapons]
-
A.
hasHistoricalPrecursor
chosen
Indicates that one entity existed earlier and served as a predecessor, model, or influential forerunner to the other in a historical context.
-
B.
wasPrecededBy
Indicates that one event, state, or entity occurred or existed earlier in time than another.
-
C.
precededByDocument
Indicates that one document occurs or is issued earlier in sequence or time than another document.
-
D.
precededByOnPlate
Indicates that one item was placed or appeared on a plate earlier in time than another item.
-
E.
precedentFor
Indicates that one situation, decision, or case serves as an authoritative example or basis for deciding or interpreting another.
- 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_69e2fabbea94819092ed41348909622f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d6ef33081908f5d36ba1ae5f473 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 4:28 a.m.