Triple
T9266930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London 2012 Olympic Torch Relay |
E222723
|
entity |
| Predicate | torchMaterial |
P618
|
FINISHED |
| Object | aluminium alloy |
—
|
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: aluminium alloy | Statement: [London 2012 Olympic Torch Relay, torchMaterial, aluminium alloy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: torchMaterial Context triple: [London 2012 Olympic Torch Relay, torchMaterial, aluminium alloy]
-
A.
exampleMaterial
Indicates that something serves as a representative or illustrative material or sample of something else.
-
B.
pylonMaterial
Indicates that a pylon is made of, constructed from, or primarily composed of a specified material.
-
C.
materialParameter
Indicates a relationship where a specific parameter or property is associated with, or characterizes, a material in a given context.
-
D.
materialCompatibility
Indicates that two or more materials are suitable to be used together without causing adverse interactions, degradation, or performance issues.
-
E.
material
chosen
Indicates that one entity is physically composed of, made from, or constructed using the substance or material represented by the other entity.
- 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_69ca841f2e808190a64f4c31903a1332 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd074bac9481909419988a9e8d9bd5 |
completed | April 1, 2026, 11:53 a.m. |
| PD | Predicate disambiguation | batch_69cc7a537bbc8190baee71f556e52a7b |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:33 p.m.