Triple
T15984593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Canadian Navy coastal defence fleet |
E387659
|
entity |
| Predicate | vesselSuperstructureMaterial |
P121167
|
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: [Royal Canadian Navy coastal defence fleet, vesselSuperstructureMaterial, aluminium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vesselSuperstructureMaterial Context triple: [Royal Canadian Navy coastal defence fleet, vesselSuperstructureMaterial, aluminium]
-
A.
boatConstructionMaterial
Indicates the material from which a boat is (or was) constructed.
-
B.
hullConstruction
Indicates the process or activity of building, assembling, or forming the main body (hull) of a vessel or similar structure.
-
C.
sailMaterial
Indicates the material from which a sail is made or constructed.
-
D.
shipMaterial
Indicates that one entity is the material or substance from which the ship entity is made or constructed.
-
E.
featuresVessel
Indicates that one entity includes, presents, or prominently displays a particular vessel as part of its composition, content, or configuration.
- 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_69d86daa562c81908aacc179c0fe8fb5 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d9d8e881909b559a3e3ca21d24 |
completed | April 16, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69e17d48cc9c8190b03fd07ae2e9dfd8 |
completed | April 17, 2026, 12:22 a.m. |
Created at: April 10, 2026, 4:54 a.m.