Triple
T2227472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virginia Company of London |
E48684
|
entity |
| Predicate | charterFeature |
P36342
|
FINISHED |
| Object | right to govern settlers |
—
|
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: right to govern settlers | Statement: [Virginia Company of London, charterFeature, right to govern settlers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: charterFeature Context triple: [Virginia Company of London, charterFeature, right to govern settlers]
-
A.
charterType
Indicates the specific category or kind of charter under which an entity, agreement, or operation is formally established or governed.
-
B.
policyCharacteristic
Indicates that a policy possesses a particular attribute, feature, or quality that characterizes how it is defined or operates.
-
C.
charterRevised
Indicates that an existing charter has been modified or updated from its previous version.
-
D.
hasCharter
Indicates that an entity possesses, is governed by, or operates under a formal charter or foundational document.
-
E.
clubCharter
Indicates that there exists a formal charter or foundational document that defines the rules, purpose, and governance structure of a club.
- 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_69a88aa51b388190949868ec9766e587 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc0670ce48190b98814064bff0517 |
completed | March 7, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69abbdadbb0c8190b3a1ede31b8acbfa |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbe4252688190944491a450383450 |
completed | March 7, 2026, 5:57 a.m. |
Created at: March 4, 2026, 7:47 p.m.