Triple
T3714987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingston-class coastal defence vessel |
E81505
|
entity |
| Predicate | hasSuperstructureMaterial |
P1272
|
FINISHED |
| Object | aluminium |
—
|
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 | Statement: [Kingston-class coastal defence vessel, hasSuperstructureMaterial, aluminium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuperstructureMaterial Context triple: [Kingston-class coastal defence vessel, hasSuperstructureMaterial, aluminium]
-
A.
hasStationBuildingMaterial
Indicates that a station’s building is constructed from, or primarily composed of, a specified material.
-
B.
hasSuperstrate
Indicates that one material, layer, or structure lies above and is supported by another in a layered or composite arrangement.
-
C.
hasDomeMaterial
Indicates that the material specified is used as the primary construction or covering material of a dome.
-
D.
materialUsed
chosen
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
E.
exteriorMaterial
Indicates the material that forms the outer surface or outer construction of an object or structure.
- 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_69ad8b1a81588190b3f27a5483bb610e |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adc9ce253c8190ada8eaa395fd3d5c |
completed | March 8, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69adc0436e508190909ec4a3e8443aef |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:33 p.m.