Triple
T20063930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maryland proprietors |
E499556
|
entity |
| Predicate | lostDirectControl |
P78345
|
FINISHED |
| Object | 1691 |
—
|
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: 1691 | Statement: [Maryland proprietors, lostDirectControl, 1691]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lostDirectControl Context triple: [Maryland proprietors, lostDirectControl, 1691]
-
A.
lostEffectiveControlOf
Indicates that an entity no longer has practical or functional authority, influence, or command over another entity, asset, or domain, even if formal or legal control may still exist.
-
B.
lostAuthorityOver
chosen
Indicates that an entity no longer holds control, power, or decision-making authority over another entity or domain it previously governed.
-
C.
lostSupportOf
Indicates that one entity no longer has the backing, approval, or endorsement of another entity that previously supported it.
-
D.
lostWith
Indicates that one entity experienced a loss or defeat in conjunction with, or as part of the same side/team as, another entity.
-
E.
endedControlOf
Indicates that one entity has ceased to exercise authority, influence, or governance over another entity 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_69da6276bcf48190aabbf279192a5fb4 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66377b6b48190a0a37279f285123e |
completed | April 20, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:39 p.m.