Triple
T30765019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victor V |
E783343
|
entity |
| Predicate | hasCodenameSeries |
P203499
|
FINISHED |
| Object | Victor operations |
—
|
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: Victor operations | Statement: [Victor V, hasCodenameSeries, Victor operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCodenameSeries Context triple: [Victor V, hasCodenameSeries, Victor operations]
-
A.
hasCodenameLanguage
Indicates that a codename is expressed or defined in a particular language.
-
B.
relatedCodename
Indicates that one entity has an associated or connected codename that is contextually related to it.
-
C.
successorCodename
Indicates that one codename directly follows and replaces another in a sequence or lifecycle.
-
D.
servesCodename
Indicates that one entity provides or uses another entity under a specific codename or alias.
-
E.
usesCodenameTheme
Indicates that an entity adopts a consistent codename pattern or motif (e.g., colors, planets, mythological figures) for naming related items or agents.
- F. None of above. chosen
Provenance (4 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_69f224b047f48190b4f5efeb7ee97b37 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a0191d96dc88190ac0823e534f9d704 |
completed | May 11, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_6a01908110448190a46442ffe4d15f5f |
completed | May 11, 2026, 8:17 a.m. |
| PDg | Predicate description generation | batch_6a0191d8cc888190859143c9e459653a |
completed | May 11, 2026, 8:22 a.m. |
Created at: April 29, 2026, 8:39 p.m.