Triple
T38602722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CVS-14 |
E934257
|
entity |
| Predicate | shipTypeAfterReclassification |
P185470
|
FINISHED |
| Object | anti-submarine aircraft carrier |
—
|
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: anti-submarine aircraft carrier | Statement: [CVS-14, shipTypeAfterReclassification, anti-submarine aircraft carrier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shipTypeAfterReclassification Context triple: [CVS-14, shipTypeAfterReclassification, anti-submarine aircraft carrier]
-
A.
shipClass
Indicates the classification or type category to which a particular ship belongs.
-
B.
shipRoleClass
chosen
Indicates the specific functional role or classification assigned to a ship within a broader maritime or operational context.
-
C.
IMOCategory
Indicates the classification of an entity according to the International Mathematical Olympiad (IMO) category it belongs to.
-
D.
shipTypeProduced
Indicates that a particular type of ship is produced, built, or manufactured by a given entity.
-
E.
navalStandardType
Indicates the specific naval standard or classification system under which an entity (such as a vessel, equipment, or procedure) is defined or regulated.
- 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_69f76ecc17688190b389b693a5927501 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.