Triple
T30712512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Action of 20 February 1815 |
E781929
|
entity |
| Predicate | USShipNicknameInvolved |
P170054
|
FINISHED |
| Object | Old Ironsides |
—
|
NE NERFINISHED |
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: Old Ironsides | Statement: [Action of 20 February 1815, USShipNicknameInvolved, Old Ironsides]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: USShipNicknameInvolved Context triple: [Action of 20 February 1815, USShipNicknameInvolved, Old Ironsides]
-
A.
notableVictimShip
Indicates that a ship is recognized as a particularly significant or noteworthy victim in a specific incident or context.
-
B.
USNDesignation
Indicates the formal designation assigned by the United States Navy to identify and classify a ship, aircraft, or other naval asset.
-
C.
notableShip
Indicates that there is a notable or significant ship associated with the subject entity.
-
D.
namesakeShip
Indicates that one entity is a ship that is named after, or serves as the namesake of, another entity.
-
E.
shipName
Indicates the name assigned to a specific ship in the relationship.
- F. None of above. chosen
Provenance (4 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_69f224acd24481908ed5f96f0d69b5dd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68c1fd1e081908fa0a55e82f3030b |
completed | May 2, 2026, 11:43 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f688034580819086a0f9100645f8ba |
completed | May 2, 2026, 11:25 p.m. |
Created at: April 29, 2026, 8:35 p.m.