Triple
T38602732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CVS-14 |
E934257
|
entity |
| Predicate | suffixLetterMeaning |
P47684
|
FINISHED |
| Object | S indicates anti-submarine warfare |
—
|
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: S indicates anti-submarine warfare | Statement: [CVS-14, suffixLetterMeaning, S indicates anti-submarine warfare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suffixLetterMeaning Context triple: [CVS-14, suffixLetterMeaning, S indicates anti-submarine warfare]
-
A.
letterMeaning
chosen
Indicates that a particular letter conveys a specific meaning, interpretation, or semantic content.
-
B.
etymologySuffix
Indicates that one term functions as a suffix in the etymological formation or derivation of another term.
-
C.
lettersMeaning
Indicates that a set of letters or characters represents, signifies, or conveys a particular meaning or message.
-
D.
suffixMeaningOf_ko
Indicates that the suffix “ko” expresses a particular meaning or grammatical function in relation to the base word or stem.
-
E.
hasLastThreeLettersMeaning
Indicates that the last three letters of one entity (typically a word or string) together form a meaningful unit or have a specific semantic significance.
- 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.