Triple
T19115591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ohio Company of Virginia |
E467898
|
entity |
| Predicate | soughtToControl |
P69335
|
FINISHED |
| Object | trade in the Ohio Country |
—
|
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: trade in the Ohio Country | Statement: [Ohio Company of Virginia, soughtToControl, trade in the Ohio Country]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soughtToControl Context triple: [Ohio Company of Virginia, soughtToControl, trade in the Ohio Country]
-
A.
aimsToControl
chosen
Indicates an intention or effort by one entity to gain power over, direct, or regulate another entity or situation.
-
B.
usedToControl
Indicates that one entity employed another as a means or tool to exercise control or regulation over something.
-
C.
endedControlOf
Indicates that one entity has ceased to exercise authority, influence, or governance over another entity or domain.
-
D.
affectedControlOf
Indicates that one entity has influenced, altered, or impacted the degree of control another entity has over something.
-
E.
controlledIn
Indicates that one entity exercised control, authority, or governance over another entity within a specific context or domain.
- 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_69d8dd06a26481908039e2a1bae8c597 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e39736588190b80ddef77101641a |
completed | April 20, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b085288190b974d649e12e0844 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.