Triple
T36997312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Bennett (DD-473) |
E915262
|
entity |
| Predicate | transferredOn |
P153246
|
FINISHED |
| Object | 1959-12-15 |
—
|
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: 1959-12-15 | Statement: [USS Bennett (DD-473), transferredOn, 1959-12-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transferredOn Context triple: [USS Bennett (DD-473), transferredOn, 1959-12-15]
-
A.
dateOfTransfer
chosen
Indicates the specific date on which a transfer of something (such as ownership, rights, or funds) from one party to another takes place.
-
B.
transferCompletedOn
Indicates that a transfer action has been fully completed at or by a specific point in time.
-
C.
officeTransferredAt
Indicates the time or date at which an office (or official position) was transferred from one holder or location to another.
-
D.
depositedOn
Indicates that one entity has placed or stored something onto or into another entity, typically as part of a deposit or accumulation process.
-
E.
transferredWith
Indicates that something was moved or conveyed from one entity to another using a specified medium, method, or accompanying item.
- 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_69f76e8f1a8c81909db172ed31304971 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffac35ac5481908b6bdfd5bbe8c76e |
completed | May 9, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69ffabbfd2548190964c851496bbbaee |
completed | May 9, 2026, 9:48 p.m. |
Created at: May 3, 2026, 4:14 p.m.