Triple
T10930738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colony of Georgia |
E258197
|
entity |
| Predicate | becameRoyalColony |
P6044
|
FINISHED |
| Object | 1752 |
—
|
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: 1752 | Statement: [Colony of Georgia, becameRoyalColony, 1752]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becameRoyalColony Context triple: [Colony of Georgia, becameRoyalColony, 1752]
-
A.
representedColony
Indicates that an entity acted as an official representative or delegate for a particular colony in some context or event.
-
B.
foundedAsColonyFor
Indicates that one entity was established as a colony specifically for the benefit, use, or purposes of another entity.
-
C.
formerColonialStatus
Indicates that one entity previously held colonial authority or control over another entity, but that colonial relationship has since ended.
-
D.
endedAsColony
Indicates that an entity ultimately ceased to exist as an independent polity and finished its historical trajectory under colonial rule by another power.
-
E.
broughtUnderBritishCrown
chosen
Indicates that an entity was placed under the authority, control, or sovereignty of the British Crown.
- 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_69d6aa8769b4819082bfe5e61b9017f0 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7709f92088190a15ae3638d3b14fb |
completed | April 9, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69d72e799f808190b6ab64fc7586a303 |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:22 p.m.