Triple
T28141959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sir John Colleton |
E714364
|
entity |
| Predicate | legalStatusInCarolina |
P192557
|
FINISHED |
| Object | proprietor |
—
|
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: proprietor | Statement: [Sir John Colleton, legalStatusInCarolina, proprietor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusInCarolina Context triple: [Sir John Colleton, legalStatusInCarolina, proprietor]
-
A.
legalStatusAtIssue
Indicates that the legal status of an entity is the central subject of dispute, consideration, or determination in a legal context.
-
B.
legalCodeStatus
Indicates the legal or regulatory status assigned to a specific code within a legal or statutory system (e.g., active, repealed, pending).
-
C.
lawCodeStatus
Indicates the legal status or condition assigned to a law code within a given legal or regulatory framework.
-
D.
legalStatusVariesBy
Indicates that the legal status of something differs depending on a specified jurisdiction, context, or set of conditions.
-
E.
stateOfLicense
Indicates the jurisdiction or state that has issued or governs the relevant license.
- 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_69efd6af156c81908f50c2cd7db0e1ef |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
| PDg | Predicate description generation | batch_69fd19f6a7888190aa7eee2b87687c53 |
completed | May 7, 2026, 11:02 p.m. |
Created at: April 27, 2026, 9:54 p.m.