Triple
T28744270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord of the Mercians |
E731323
|
entity |
| Predicate | rankComparedToKing |
P156652
|
FINISHED |
| Object | below king |
—
|
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: below king | Statement: [Lord of the Mercians, rankComparedToKing, below king]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankComparedToKing Context triple: [Lord of the Mercians, rankComparedToKing, below king]
-
A.
rankRelativeToKing
chosen
Indicates that one entity holds a specific hierarchical rank or status in relation to a king.
-
B.
rankComparedTo
Indicates the relative ordering or position of one entity in comparison to another based on a specified ranking criterion.
-
C.
positionOnKing
Indicates that one entity occupies a specific positional relationship relative to a king in a given context.
-
D.
rankBeforeKingship
Indicates that one entity held a higher or earlier rank or status than another entity prior to that other entity attaining kingship.
-
E.
evaluatesKingsBy
Indicates a relationship where an agent assesses or judges kings according to a specified criterion, standard, or method.
- 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_69f043ecb5c081909ec9da1172d68ece |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f657b646e0819092c5526d83ecdc6a |
completed | May 2, 2026, 7:59 p.m. |
| PD | Predicate disambiguation | batch_69f651ada6048190a7b4a6981565dc3a |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 6:04 a.m.