Triple
T11388977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Gleaves (DD-423) |
E269782
|
entity |
| Predicate | servedUntilEra |
P37781
|
FINISHED |
| Object | immediately post-World War II |
—
|
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: immediately post-World War II | Statement: [USS Gleaves (DD-423), servedUntilEra, immediately post-World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedUntilEra Context triple: [USS Gleaves (DD-423), servedUntilEra, immediately post-World War II]
-
A.
servedUntil
chosen
Indicates the ending time or date up to which an entity held a position, role, or service.
-
B.
endedEra
Indicates that one entity brought about or marked the conclusion of a particular era associated with another entity.
-
C.
appliesToEra
Indicates that something is relevant, valid, or in effect during a particular historical or temporal era.
-
D.
serviceEra
Indicates the historical period or era during which a service, role, or duty was performed.
-
E.
partOfEra
Indicates that one entity exists as a temporal segment or component within the duration or scope of a larger historical era.
- 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_69d6aacdbc6c8190af6dc3d5f5d22836 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d800160a1c81909d115bf89fe54a49 |
completed | April 9, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69d7e70b228c8190b87f5101fd683788 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:34 p.m.