Triple
T37425371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mingoes |
E929972
|
entity |
| Predicate | colonialDesignationBy |
P17271
|
FINISHED |
| Object | British 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: British colonists | Statement: [Mingoes, colonialDesignationBy, British colonists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colonialDesignationBy Context triple: [Mingoes, colonialDesignationBy, British colonists]
-
A.
colonialDesignation
Indicates that one entity assigns or holds a status, name, or classification for another entity within a colonial or colonially imposed framework.
-
B.
hasColonialName
Indicates that an entity is known by, or has been assigned, a name originating from a colonial power or colonial period.
-
C.
hasColonialAdministrativeCategory
Indicates that an entity is classified under a specific category within a colonial administrative system or hierarchy.
-
D.
colonialNameUsedBy
chosen
Indicates that a colonial-era name for a place, group, or entity is used or applied by a particular agent or source.
-
E.
representedColony
Indicates that an entity acted as an official representative or delegate for a particular colony in some context or event.
- 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_69f76ebf0f288190ba198a78341613b8 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:16 p.m.