Triple
T38602749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CVS-14 |
E934257
|
entity |
| Predicate | associatedShipServiceEntryPeriod |
P17164
|
FINISHED |
| Object | World War II era |
—
|
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: World War II era | Statement: [CVS-14, associatedShipServiceEntryPeriod, World War II era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedShipServiceEntryPeriod Context triple: [CVS-14, associatedShipServiceEntryPeriod, World War II era]
-
A.
associatedPeriodEnd
Indicates the ending point or final date of the time period with which something is associated.
-
B.
serviceEntryPeriod
chosen
Indicates the span of time during which a service is active, valid, or in effect for the related entities.
-
C.
periodAssociatedWith
Indicates an association or linkage between something and a specific time period or temporal span.
-
D.
shipAssociatedWith
Indicates that there is a relevant connection or involvement between a ship and another entity, such as ownership, operation, registration, or functional association.
-
E.
hasPeriodOf
Indicates that one entity possesses, experiences, or is associated with a specific span or interval of time.
- 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_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.