Triple
T10430412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mise of Lewes agreement |
E245896
|
entity |
| Predicate | temporarilyTransferredPowerTo |
P71468
|
FINISHED |
| Object | baronial council |
—
|
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: baronial council | Statement: [Mise of Lewes agreement, temporarilyTransferredPowerTo, baronial council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporarilyTransferredPowerTo Context triple: [Mise of Lewes agreement, temporarilyTransferredPowerTo, baronial council]
-
A.
transferredPowerTo
chosen
Indicates that one entity has passed control, authority, or energy to another entity.
-
B.
heldTemporalPower
Indicates that an entity exercised governing or authoritative control over another entity or domain during a specific period of time.
-
C.
lostTemporalPower
Indicates that an entity has ceased to hold or exercise secular or time-bound authority or control it previously possessed.
-
D.
inPowerDuring
Indicates that an entity holds a position of authority or governance throughout a specified time period.
-
E.
plannedPowerExportTo
Indicates that one entity has scheduled or intends to transfer a specified amount of electrical power to another entity.
- 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea62d6448190a7f5b785467824cf |
completed | April 7, 2026, 11:28 a.m. |
| PD | Predicate disambiguation | batch_69d4dfbc546881908f312c66ee195f79 |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:13 p.m.