Triple
T25303938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Historic Inner City of Paramaribo |
E634428
|
entity |
| Predicate | foundedAsColonialTownBy |
P76009
|
FINISHED |
| Object | Dutch colonists |
—
|
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 colonists | Statement: [Historic Inner City of Paramaribo, foundedAsColonialTownBy, Dutch colonists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsColonialTownBy Context triple: [Historic Inner City of Paramaribo, foundedAsColonialTownBy, Dutch colonists]
-
A.
foundedAsColonyFor
Indicates that one entity was established as a colony specifically for the benefit, use, or purposes of another entity.
-
B.
colonyFoundedBy
chosen
Indicates that a particular colony was established or created by a specific founding entity (such as a person, group, or organization).
-
C.
colonyFounded
Indicates that an entity established or created a colony at a particular time or place.
-
D.
foundedAsColonyOf
Indicates that an entity was originally established as a colony under the control or authority of another entity.
-
E.
regionOfColonyFounded
Indicates the geographic region in which a particular colony was originally founded.
- 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_69e75a972c6481909bc11710e8d30a6c |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f627aedf548190bc9f53c8a2d67b50 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 21, 2026, 1:25 p.m.