Triple
T27623339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle between USS Constitution and HMS Guerriere |
E696136
|
entity |
| Predicate | USShipCommander |
P90806
|
FINISHED |
| Object | Isaac Hull |
—
|
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: Isaac Hull | Statement: [Battle between USS Constitution and HMS Guerriere, USShipCommander, Isaac Hull]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: USShipCommander Context triple: [Battle between USS Constitution and HMS Guerriere, USShipCommander, Isaac Hull]
-
A.
fleetCommander
Indicates that one entity serves as the commanding officer or overall leader in charge of the operations and decisions of a fleet associated with another entity.
-
B.
fireshipForceCommander
Indicates that an entity serves as the commanding officer responsible for directing and overseeing fireship operations.
-
C.
USShipRate
Indicates the rate or cost at which items are shipped within, from, or to the United States.
-
D.
fleetCommander (British)
Indicates that the subject serves as the fleet commander for the British naval forces.
-
E.
shipOwnedOrCommanded
chosen
Indicates that an entity either owns a ship or serves as its commanding authority.
- 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_69ef59092c8881908114ad184248cc46 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f630de07c48190b18cffe15ac20618 |
completed | May 2, 2026, 5:14 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:16 p.m.