Triple
T20063931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maryland proprietors |
E499556
|
entity |
| Predicate | restoredToPower |
P3243
|
FINISHED |
| Object | 1715 |
—
|
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: 1715 | Statement: [Maryland proprietors, restoredToPower, 1715]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restoredToPower Context triple: [Maryland proprietors, restoredToPower, 1715]
-
A.
regainedPowerAgainIn
Indicates that an entity, having previously lost power, has once more returned to a position of power or control within a specified context or location.
-
B.
lostPowerAfter
Indicates that one entity ceased to have power or electricity following an event associated with another entity.
-
C.
restored
Indicates that an entity has returned another entity to a previous or improved state, condition, or position after damage, loss, or alteration.
-
D.
regainedPowerIn
chosen
Indicates that an entity has recovered or reestablished its previous level of power, control, or authority within a specified context or domain.
-
E.
lostPowerAgainIn
Indicates that an entity has experienced a repeated loss of power in a specified location or context.
- 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.