Triple
T257533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Province of South Carolina |
E5467
|
entity |
| Predicate | colonialStatusChanged |
P7797
|
FINISHED |
| Object | royal colony in 1719 |
—
|
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: royal colony in 1719 | Statement: [Province of South Carolina, colonialStatusChanged, royal colony in 1719]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colonialStatusChanged Context triple: [Province of South Carolina, colonialStatusChanged, royal colony in 1719]
-
A.
colonialOffshoot
Indicates that one entity originated as a colony or derivative settlement established by another entity.
-
B.
hadColonialAdministrationType
Indicates the specific form or system of colonial governance that was exercised over a territory or population.
-
C.
territorialStatus
Indicates the legal or political condition of control, sovereignty, or jurisdiction that applies to a specific territory.
-
D.
wasColonyOf
Indicates that one entity functioned as a colony under the political control or administration of another entity.
-
E.
successorTerritorialStatus
chosen
Indicates the territorial status or jurisdiction that directly follows and replaces a previous territorial status in a succession or transition.
- 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_69a2580a64ac8190ad76e34bb0715b5e |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25d703e688190bb86c69527e306f5 |
completed | Feb. 28, 2026, 3:13 a.m. |
| PD | Predicate disambiguation | batch_69a25b694c08819085bb4b256fa7736f |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:55 a.m.