Triple
T8216445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1st Cruiser Squadron |
E191942
|
entity |
| Predicate | typicalFlagshipType |
P36594
|
FINISHED |
| Object | armoured cruiser |
—
|
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 cruiser | Statement: [1st Cruiser Squadron, typicalFlagshipType, armoured cruiser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFlagshipType Context triple: [1st Cruiser Squadron, typicalFlagshipType, armoured cruiser]
-
A.
flagshipType
chosen
Indicates that one entity is the primary or most important representative (flagship) of a particular type, category, or group defined by the other entity.
-
B.
isFlagshipServiceOf
Indicates that a particular service is the primary, leading, or most prominent offering of a given organization or provider.
-
C.
typicalFeatures
Indicates that the related entities are characteristic or commonly occurring features or attributes of something.
-
D.
hasFlagshipIn
Indicates that an entity designates a particular location or branch as its primary or flagship presence.
-
E.
originalFlagshipName
Indicates the original name by which a flagship entity (such as a primary product, vessel, or brand) was first designated or known.
- 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_69ca82c8c054819087fedd9a5436b8a3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb776dcfa08190969863b886336c91 |
completed | March 31, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69cb36ad01ac81909609b15f6a6c8581 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:44 p.m.