Triple
T21789427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlantic campaign of 1806 |
E537929
|
entity |
| Predicate | seaLaneContested |
P145655
|
FINISHED |
| Object | transatlantic trade routes |
—
|
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: transatlantic trade routes | Statement: [Atlantic campaign of 1806, seaLaneContested, transatlantic trade routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seaLaneContested Context triple: [Atlantic campaign of 1806, seaLaneContested, transatlantic trade routes]
-
A.
islandContested
Indicates that control or ownership of an island is disputed or contested between two or more parties.
-
B.
belligerentControl
Indicates that one party exercises control, authority, or coercive influence over another in a hostile or conflict-oriented context.
-
C.
capitalContested
Indicates that the status of being the capital of a region or country is disputed or claimed by multiple parties.
-
D.
contestedBy
Indicates that one party challenges, disputes, or opposes a claim, decision, or position held by another party.
-
E.
isContestedRegion
Indicates that a geographic area is claimed or disputed by two or more parties regarding its ownership, control, or status.
- 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_69e0c47198f881908cb0d237266c10e9 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0621ed2b481909e3df17aee9cd8f7 |
completed | April 28, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69e6be751ce881909badced245ef76c7 |
completed | April 21, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69e6c3a2898881909748935cf92f898c |
completed | April 21, 2026, 12:24 a.m. |
Created at: April 16, 2026, 6:52 p.m.