Triple
T24738948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trio people |
E618494
|
entity |
| Predicate | mainAreaInSuriname |
P19488
|
FINISHED |
| Object | southern Suriname |
—
|
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: southern Suriname | Statement: [Trio people, mainAreaInSuriname, southern Suriname]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainAreaInSuriname Context triple: [Trio people, mainAreaInSuriname, southern Suriname]
-
A.
isOneOfMainAreasFor
Indicates that something belongs to the primary set of domains, topics, or fields associated with another entity.
-
B.
primaryArea
chosen
Indicates that one entity is the main or most important area, domain, or field associated with another entity.
-
C.
associatedMainlandArea
Indicates a relationship where a non-mainland region (such as an island or territory) is linked to the specific mainland area with which it is geographically, administratively, or politically connected.
-
D.
hasMajorRainforest
Indicates that one entity possesses or contains a large, significant rainforest within its area or domain.
-
E.
primarySourceArea
Indicates that something originates from, or is chiefly derived from, a specified source area.
- 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_69e2fab8f95c81908bb9e552cf3280c2 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f422aee0408190899efe7e24ef2b40 |
completed | May 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f420e92cc88190a803aecdae78a051 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 4:04 a.m.