Triple
T31610098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS American Victory |
E806601
|
entity |
| Predicate | USMCNumber |
P79763
|
FINISHED |
| Object | V-795 |
—
|
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: V-795 | Statement: [SS American Victory, USMCNumber, V-795]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: USMCNumber Context triple: [SS American Victory, USMCNumber, V-795]
-
A.
designationByUSMC
chosen
Indicates that an entity has been formally assigned a specific designation or identifier by the United States Marine Corps (USMC).
-
B.
isMarineCorpsEquivalent
Indicates that one military unit, rank, or organization is considered the functional or structural counterpart of another within a Marine Corps context.
-
C.
militaryServiceNumber
Indicates the unique identification number assigned to an individual for tracking their record in a military service context.
-
D.
regimentalNumber
Indicates the unique identifying number assigned to a member of a regiment, linking an individual to their specific regimental record.
-
E.
usArmyDesignation
Indicates the specific designation or code assigned to something by the United States Army.
- 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_69f348d61f2081908cad94bc9ffbb671 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a873357481909a3499827e927cda |
completed | May 3, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:36 p.m.