Triple
T354939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eleanor |
E7522
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ship involved in the Boston Tea Party |
C959
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: ship involved in the Boston Tea Party Context triple: [Eleanor, instanceOf, ship involved in the Boston Tea Party]
-
A.
event in the War of 1812
An "event in the War of 1812" is a specific historical occurrence—such as a battle, treaty, political decision, or military campaign—that took place between 1812 and 1815 and directly relates to the conflict between the United States, the United Kingdom, and their respective allies.
-
B.
British merchant ship
chosen
A British merchant ship is a civilian vessel registered under the British flag and used primarily for commercial trade, transport of goods, and sometimes passengers across domestic and international waters.
-
C.
colonial-era event
A colonial-era event is a historically significant occurrence that took place during a period when one nation exercised political, economic, or cultural control over foreign territories and populations.
-
D.
United States Navy ship
A United States Navy ship is a commissioned naval vessel operated by the U.S. Navy, designed, equipped, and crewed to perform military, logistical, and support missions at sea and in littoral environments.
-
E.
era in United States history
An era in United States history is a distinct time period characterized by particular political, social, economic, and cultural conditions or transformative events that differentiate it from other periods.
- F. None of above.
Provenance (1 batch)
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_69a2e7e696948190bebc966535995e45 |
completed | Feb. 28, 2026, 1:04 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.