Triple
T24959051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CL-47 |
E624552
|
entity |
| Predicate | vesselDisplacementClass |
P24307
|
FINISHED |
| Object | light cruiser category |
—
|
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: light cruiser category | Statement: [CL-47, vesselDisplacementClass, light cruiser category]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vesselDisplacementClass Context triple: [CL-47, vesselDisplacementClass, light cruiser category]
-
A.
tonnageClass
chosen
Indicates a classification relationship where an entity is assigned to a category based on its tonnage (weight or carrying capacity range).
-
B.
IMOCategory
Indicates the classification of an entity according to the International Mathematical Olympiad (IMO) category it belongs to.
-
C.
standardDisplacement
Indicates the typical or officially specified amount of displacement (such as volume, weight, or capacity) associated with an entity under standard conditions.
-
D.
vesselDesignation
Indicates that a specific identifying designation (such as a name, number, or code) is assigned to a vessel.
-
E.
shipClass
Indicates the classification or type category to which a particular ship belongs.
- 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_69e2ff23a3a88190b1b9743fe5e15f94 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f4242b03a081909c676b1884191f17 |
completed | May 1, 2026, 3:55 a.m. |
| PD | Predicate disambiguation | batch_69f4210130d08190ae30b7943f7a0bbc |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:58 a.m.