Triple
T4637995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japanese battlecruiser Amagi |
E101580
|
entity |
| Predicate | plannedArmour |
P6071
|
FINISHED |
| Object | armoured belt |
—
|
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: armoured belt | Statement: [Japanese battlecruiser Amagi, plannedArmour, armoured belt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedArmour Context triple: [Japanese battlecruiser Amagi, plannedArmour, armoured belt]
-
A.
armour
chosen
Indicates that an entity provides protective covering or defense for another entity.
-
B.
combatArm
Indicates that one entity serves as a primary fighting or operational warfare branch or component of another entity (such as an organization or military force).
-
C.
militaryProject
Indicates a project that is conducted, funded, or controlled by a military organization, typically for defense, security, or warfare-related purposes.
-
D.
numberOfPlannedShips
Indicates the total count of ships that are intended or scheduled to be built, deployed, or used according to a plan.
-
E.
militaryEquivalence
Indicates that two or more entities possess comparable military capabilities, strength, or strategic power such that neither holds a clear military advantage over the other.
- 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_69bd43d3bc7c81908f81fcf380476b0f |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a64214481908a207e8070cc7a45 |
completed | March 20, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69bd5233cb5081908807e2b150f0ca06 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:13 p.m.