Triple
T17518466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amarr Empire |
E426625
|
entity |
| Predicate | shipDesignPhilosophy |
P127747
|
FINISHED |
| Object | heavy armor tanks |
—
|
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: heavy armor tanks | Statement: [Amarr Empire, shipDesignPhilosophy, heavy armor tanks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shipDesignPhilosophy Context triple: [Amarr Empire, shipDesignPhilosophy, heavy armor tanks]
-
A.
shipDesigned
Indicates that one entity is responsible for designing or creating the design of a ship associated with another entity.
-
B.
sailDesign
Indicates a design relationship where one entity specifies or defines the shape, structure, or configuration of a sail used for propulsion.
-
C.
navalArchitecture
Indicates the design, engineering, and construction-related relationship between entities involved in ships or other marine vessels.
-
D.
tankDesign
Indicates a relationship where an entity is responsible for or associated with the design or engineering of a tank.
-
E.
shipDraft
Indicates the depth of a ship’s hull below the waterline, typically representing how deeply the vessel sits in the water.
- 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_69d889dd9164819087b1dc3c9240c870 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e452d0daa48190be69aff32b0324bc |
completed | April 19, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f8b9888190aa8a45e09acf4319 |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb37d148190b7f38599c06594ee |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:49 a.m.