Triple
T3919711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord High Constable of England |
E88926
|
entity |
| Predicate | eraOfGreatestPower |
P5250
|
FINISHED |
| Object | Middle Ages |
—
|
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: Middle Ages | Statement: [Lord High Constable of England, eraOfGreatestPower, Middle Ages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraOfGreatestPower Context triple: [Lord High Constable of England, eraOfGreatestPower, Middle Ages]
-
A.
eraOfMyth
Indicates a temporal relationship where an event, story, or phenomenon belongs to or takes place during a mythological or legendary era.
-
B.
eraCharacter
Indicates that a character is associated with, or belongs to, a particular historical or fictional era.
-
C.
lordOf
Indicates that one entity holds lordship, authority, or dominion over another entity.
-
D.
eraOfSignificance
chosen
Indicates the historical period or timeframe during which an entity was particularly important, influential, or noteworthy.
-
E.
powerBehindThrone
Indicates a relationship where one entity secretly or informally controls or strongly influences the authority and decisions of another entity that holds the official position of power.
- 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_69aed955229881909e85e73ffab1d343 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef188b474819087680db42b04ecdd |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee75eedcc81908088ff4dbb8be56b |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:22 p.m.