Triple
T30732135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carolina (colony) |
E782450
|
entity |
| Predicate | splitIntoSeparateColonies |
P170079
|
FINISHED |
| Object | North Carolina |
—
|
NE NERFINISHED |
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: North Carolina | Statement: [Carolina (colony), splitIntoSeparateColonies, North Carolina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: splitIntoSeparateColonies Context triple: [Carolina (colony), splitIntoSeparateColonies, North Carolina]
-
A.
mergedColonies
Indicates that two or more previously separate colonies have been combined into a single unified colony.
-
B.
numberOfColonies
Indicates the count of distinct colonies associated with or possessed by a given entity.
-
C.
endedAsColony
Indicates that an entity ultimately ceased to exist as an independent polity and finished its historical trajectory under colonial rule by another power.
-
D.
separatesFormerColoniesOf
Indicates a relationship where something serves as a dividing boundary or barrier between territories that were once colonies of the same colonizing power.
-
E.
colonyOf
Indicates that one entity is a colony belonging to, founded by, or politically dependent on another entity.
- 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68ee47d048190a0fe21f41556774f |
completed | May 2, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f688034580819086a0f9100645f8ba |
completed | May 2, 2026, 11:25 p.m. |
Created at: April 29, 2026, 8:37 p.m.