Triple
T16288993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishop of Thérouanne |
E395466
|
entity |
| Predicate | heldTemporalPowers |
P29191
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Bishop of Thérouanne, heldTemporalPowers, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldTemporalPowers Context triple: [Bishop of Thérouanne, heldTemporalPowers, yes]
-
A.
heldTemporalPower
chosen
Indicates that an entity exercised governing or authoritative control over another entity or domain during a specific period of time.
-
B.
heldExecutivePowerUntil
Indicates that an entity exercised executive authority or leadership in a role or office up to a specified end date or point in time.
-
C.
temporalAuthorityHeldBy
Indicates that a specified temporal (non-spiritual, worldly) authority or power is held or exercised by a particular entity.
-
D.
temporarilyShiftedBalanceOfPower
Indicates a relationship where an action or event caused a non-permanent change in which party holds greater power or influence over another.
-
E.
exercisedPowerOver
Indicates that one entity exerted control, influence, or authority over 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e249165af881908ce44c4517c93c12 |
completed | April 17, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_69e219f68d308190b71c1601303f0628 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:05 a.m.