Triple
T3010478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | English forces under Richard Nicolls |
E82204
|
entity |
| Predicate | predecessorControl |
P44642
|
FINISHED |
| Object | Dutch control of New 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: Dutch control of New Amsterdam | Statement: [English forces under Richard Nicolls, predecessorControl, Dutch control of New Amsterdam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorControl Context triple: [English forces under Richard Nicolls, predecessorControl, Dutch control of New Amsterdam]
-
A.
predecessor
Indicates that one entity comes before another in an ordered sequence or succession.
-
B.
predecessorState
Indicates that one state directly precedes another in a sequence or process.
-
C.
predecessorSeries
Indicates that one series directly precedes another in an ordered sequence or lineage.
-
D.
predecessorStateConcerned
Indicates that a concern or issue present in a predecessor state is relevant to, or carried over into, the current state.
-
E.
programPredecessor
Indicates that one program temporally or logically precedes another in a sequence or hierarchy of programs.
- 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_69ad8b1eb53481908c39bbcd1ec104b2 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a4ccbf08190a7580c9e758804d0 |
completed | March 8, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69ad96180eb08190a524c5f458d41382 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f6af3881909f4547967384114c |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 3 p.m.