Triple
T28141941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sir John Colleton |
E714364
|
entity |
| Predicate | charterSubject |
P168098
|
FINISHED |
| Object | Province of Carolina |
E44437
|
NE 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: Province of Carolina | Statement: [Sir John Colleton, charterSubject, Province of Carolina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: charterSubject Context triple: [Sir John Colleton, charterSubject, Province of Carolina]
-
A.
charterDefines
Indicates that a charter specifies or establishes the rules, roles, or scope governing something.
-
B.
charterSecured
Indicates that an official charter or authorization has been successfully obtained or granted for the relevant entity or activity.
-
C.
charterRevised
Indicates that an existing charter has been modified or updated from its previous version.
-
D.
charterType
Indicates the specific category or kind of charter under which an entity, agreement, or operation is formally established or governed.
-
E.
charterFeature
Indicates that an entity (such as a service, product, or offering) includes or provides a specific feature as part of a charter or special arrangement.
- F. None of above. chosen
Provenance (5 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_69efd6af156c81908f50c2cd7db0e1ef |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f673633d288190b52ceb9f8a057c44 |
completed | May 2, 2026, 9:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a15d7a4a02c81909f3eb340eb6ad1c6 |
completed | May 26, 2026, 5:25 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 27, 2026, 9:54 p.m.