Triple
T8277696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waxhaws region |
E193586
|
entity |
| Predicate | languageOfColonialSettlers |
P82461
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Waxhaws region, languageOfColonialSettlers, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfColonialSettlers Context triple: [Waxhaws region, languageOfColonialSettlers, English]
-
A.
officialLanguageDuringColonialPeriod
Indicates that a language served as the official language of administration or governance in a territory during its colonial period.
-
B.
languageOfFounders
Indicates the language or languages spoken or used by the founders of an entity.
-
C.
hasColonialHistoryWith
Indicates that one entity has a historical relationship of colonization or being colonized involving the other entity.
-
D.
languageOfAssimilation
Indicates the language used to integrate or absorb individuals or groups into a dominant culture or society.
-
E.
colonialPowerAtFirstArrival
Indicates that a specified colonial power was the first to arrive and establish a presence or control in a given territory or region.
- 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_69ca82e217a48190880695635c44b2ed |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb79ea3fb481908b59414702a5147e |
completed | March 31, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69cb70a4525481909399d313a6247ace |
completed | March 31, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69cb76d648988190ab0669cc0592e827 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 5:51 p.m.