Triple
T10792550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Leonard F. Mason |
E254617
|
entity |
| Predicate | pennantNumberAfterTransfer |
P3153
|
FINISHED |
| Object | DD-92 |
—
|
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: DD-92 | Statement: [USS Leonard F. Mason, pennantNumberAfterTransfer, DD-92]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pennantNumberAfterTransfer Context triple: [USS Leonard F. Mason, pennantNumberAfterTransfer, DD-92]
-
A.
pennantNumber
chosen
Indicates the identifying pennant number assigned to a ship or naval vessel.
-
B.
pennantNumberForFranchise
Indicates the specific pennant (league championship) number associated with a particular sports franchise.
-
C.
previousPennantForFranchise
Indicates that one pennant (championship title or league victory) directly preceded another for the same sports franchise in chronological order.
-
D.
ownershipTransferredTo
Indicates that the legal or formal ownership of an entity has been transferred from one party to another specified party.
-
E.
transferAfter
Indicates that one entity transfers something to another entity only after a specified event or condition has occurred.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732f7ad408190af4727dd9d459498 |
completed | April 9, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69d6f316940c819092a96c429629fdef |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:17 p.m.