Triple
T13923393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copper Age |
E334799
|
entity |
| Predicate | transitionLeadsTo |
P75693
|
FINISHED |
| Object | alloying of copper with tin to produce bronze |
—
|
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: alloying of copper with tin to produce bronze | Statement: [Copper Age, transitionLeadsTo, alloying of copper with tin to produce bronze]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transitionLeadsTo Context triple: [Copper Age, transitionLeadsTo, alloying of copper with tin to produce bronze]
-
A.
transitionTo
Indicates a change in state, condition, or phase from one defined status to another.
-
B.
canLeadTo
Indicates that one entity, condition, or event has the potential to cause, result in, or bring about another.
-
C.
exitsToState
chosen
Indicates that one state or condition transitions or leads directly to another specified state.
-
D.
transitionCharacteristic
Indicates a relationship where an entity is characterized by how it changes state or condition over time or between phases.
-
E.
losesTo
Indicates that one entity is defeated by or comes out worse than another in a competitive or comparative context.
- 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_69d81c5f739081908bc05b2461f54828 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2aa5c1f481908a9d8786872f08fe |
completed | April 14, 2026, 11:53 a.m. |
| PD | Predicate disambiguation | batch_69de059e4ba881908554f72e889719fa |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:16 p.m.