Triple
T24763951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bronze |
E619527
|
entity |
| Predicate | replacedStoneFor |
P158667
|
FINISHED |
| Object | many tools and weapons in the Bronze Age |
—
|
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: many tools and weapons in the Bronze Age | Statement: [Bronze, replacedStoneFor, many tools and weapons in the Bronze Age]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedStoneFor Context triple: [Bronze, replacedStoneFor, many tools and weapons in the Bronze Age]
-
A.
suppliedStoneTo
Indicates that one entity provided or delivered stone materials to another entity.
-
B.
rebuiltInStone
Indicates that a previously existing structure was reconstructed using stone as the primary building material.
-
C.
usesOriginalStones
Indicates that something is constructed or preserved using the same stones that were part of the original structure or artifact.
-
D.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by another entity.
-
E.
replacedStation
Indicates that one station has taken the place of another station, typically succeeding it in function, service, or location.
- F. None of above. chosen
Provenance (4 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_69f47b865df48190bf4b6d3e9f9305e6 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f4682c8a3c8190adbfaac99474eaaf |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f47b7f657c81908174590c811a3cbf |
completed | May 1, 2026, 10:07 a.m. |
Created at: April 18, 2026, 4:28 a.m.