Triple
T34287718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Thomas Jefferson (1825) |
E879786
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | admiralty law case |
C25170
|
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: admiralty law case Context triple: [The Thomas Jefferson (1825), instanceOf, admiralty law case]
-
A.
law of the sea case
chosen
A law of the sea case is a legal dispute or judicial proceeding concerning the interpretation, application, or enforcement of international rules governing maritime zones, navigation rights, resource exploitation, and ocean governance.
-
B.
maritime law enforcement activity
Maritime law enforcement activity is the set of actions by authorized agencies to monitor, control, and ensure compliance with laws and regulations in maritime zones, including preventing and responding to illegal activities at sea.
-
C.
navigation law
Navigation law is a legal framework governing the rights, responsibilities, and regulations related to the movement of vessels, aircraft, or vehicles through maritime, air, or other navigable spaces.
-
D.
ancient maritime law code
An ancient maritime law code is a historically rooted legal framework that regulates seafaring conduct, trade, navigation, and dispute resolution among sailors, merchants, and coastal states.
-
E.
maritime incident
A maritime incident is any unexpected or unintended event involving a vessel or marine operation that compromises or threatens safety, the environment, property, or normal navigation at sea or in navigable waters.
- 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_69f349b6df1c81908e5e5b6c2ab6409b |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:57 a.m.