Triple
T22854350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British capture of St. Eustatius |
E566437
|
entity |
| Predicate | hasMainTarget |
P14889
|
FINISHED |
| Object | Dutch island of St. Eustatius |
—
|
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: Dutch island of St. Eustatius | Statement: [British capture of St. Eustatius, hasMainTarget, Dutch island of St. Eustatius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainTarget Context triple: [British capture of St. Eustatius, hasMainTarget, Dutch island of St. Eustatius]
-
A.
hasTarget
chosen
Indicates that one entity is directed toward, aimed at, or intended to affect another specific entity as its target.
-
B.
hasMainDestination
Indicates that an entity is primarily intended to go to, serve, or be directed toward a particular destination.
-
C.
hasMainSource
Indicates that one entity serves as the primary or principal source or origin for another entity.
-
D.
hasMainHost
Indicates that one entity serves as the primary or principal host for another entity.
-
E.
hasMainReferent
Indicates that one entity serves as the primary or central referent for another entity within a given context.
- 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_69e2458750b481908a8e4cf4609cc6cf |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17ebb4ea48190b4b865e316f6a75f |
completed | April 29, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:37 p.m.