Triple
T14807388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commander-in-Chief, Grand Fleet |
E348071
|
entity |
| Predicate | primaryAssetType |
P3744
|
FINISHED |
| Object | dreadnought battleships |
—
|
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: dreadnought battleships | Statement: [Commander-in-Chief, Grand Fleet, primaryAssetType, dreadnought battleships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryAssetType Context triple: [Commander-in-Chief, Grand Fleet, primaryAssetType, dreadnought battleships]
-
A.
primaryAsset
chosen
Indicates that one entity is the main or most important asset associated with another entity.
-
B.
assetType
Indicates the specific category or classification of an asset within a broader asset framework or system.
-
C.
primaryType
Indicates the main or most fundamental category or classification assigned to an entity, distinguishing it from any secondary or auxiliary types.
-
D.
primaryProduct
Indicates that one entity is the main or most important product associated with, produced by, or offered by another entity.
-
E.
primaryResourceType
Indicates the main or predominant type/category of resource associated with an entity or activity.
- 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_69d822ea8b7c819097dfadf3d45545e6 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decf33b6a08190ab6a4cfeda2cc09c |
completed | April 14, 2026, 11:35 p.m. |
| PD | Predicate disambiguation | batch_69de8c0ef8a4819092d84478b1f56db1 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:41 a.m.