Triple
T21718530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ROCS Po Yang (DD-10) |
E536092
|
entity |
| Predicate | shipClassOf |
P3141
|
FINISHED |
| Object | World War II–era destroyers |
—
|
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: World War II–era destroyers | Statement: [ROCS Po Yang (DD-10), shipClassOf, World War II–era destroyers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shipClassOf Context triple: [ROCS Po Yang (DD-10), shipClassOf, World War II–era destroyers]
-
A.
shipClass
chosen
Indicates the classification or type category to which a particular ship belongs.
-
B.
shipNumberInClass
Indicates the specific ordinal position or sequence number that a ship holds within its class.
-
C.
IMOCategory
Indicates the classification of an entity according to the International Mathematical Olympiad (IMO) category it belongs to.
-
D.
tonnageClass
Indicates a classification relationship where an entity is assigned to a category based on its tonnage (weight or carrying capacity range).
-
E.
shipClassVariant
Indicates that one ship class is a variant or modified version derived from another ship class.
- 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_69e0c46c6dd88190a595375fa6ebd701 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efd96cc58081908dda09819041b888 |
completed | April 27, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:47 p.m.