Triple
T24558835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sipaliwini District |
E607597
|
entity |
| Predicate | hasMaroonCommunities |
P156319
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Sipaliwini District, hasMaroonCommunities, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaroonCommunities Context triple: [Sipaliwini District, hasMaroonCommunities, true]
-
A.
hasRemoteCommunities
Indicates that an entity maintains or is associated with communities located in distant or geographically isolated areas.
-
B.
hasCommunityIn
Indicates that a community is present, active, or established within a specified location, platform, or context.
-
C.
hasLocalCommunities
Indicates that an entity is associated with or contains smaller, localized community groups within a specific area or region.
-
D.
hasCommunityArea
Indicates that an entity is associated with, located in, or belongs to a particular community area.
-
E.
hasCommunityDistrict
Indicates that an entity is located within, associated with, or falls under the jurisdiction of a specific community district.
- 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_69e2c4cae1b88190825e88d5ce8aa61e |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8f4af6481908576473adab9f6bf |
completed | April 30, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
| PDg | Predicate description generation | batch_69f2a846c5bc81909ba50cee483bea91 |
completed | April 30, 2026, 12:54 a.m. |
Created at: April 18, 2026, 2:27 a.m.