Triple
T26648680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pampus sandbank |
E668989
|
entity |
| Predicate | reasonForFortLocation |
P119202
|
FINISHED |
| Object | control of shipping route to Amsterdam |
—
|
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: control of shipping route to Amsterdam | Statement: [Pampus sandbank, reasonForFortLocation, control of shipping route to Amsterdam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForFortLocation Context triple: [Pampus sandbank, reasonForFortLocation, control of shipping route to Amsterdam]
-
A.
reasonForFortification
chosen
Indicates the underlying motivation or purpose for which a fortification was constructed, strengthened, or maintained.
-
B.
fortressLocation
Indicates that a fortress is located at or in a specified place or geographic area.
-
C.
reasonForLocation
Indicates the cause, purpose, or justification for why an entity is at a particular location.
-
D.
reasonForRaid
Indicates the underlying cause, motive, or justification for which a raid was initiated or carried out.
-
E.
locatedInFortress
Indicates that an entity is situated within the boundaries or interior of a fortress.
- 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_69ee9d00eb5481908d6c6d0ada2f0c9a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 27, 2026, 2:32 a.m.