Triple
T28159701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kings of Mercia |
E714856
|
entity |
| Predicate | mostPowerfulKing |
P164080
|
FINISHED |
| Object | Offa of Mercia |
—
|
NE NERFINISHED |
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: Offa of Mercia | Statement: [Kings of Mercia, mostPowerfulKing, Offa of Mercia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mostPowerfulKing Context triple: [Kings of Mercia, mostPowerfulKing, Offa of Mercia]
-
A.
kingOf
Indicates that one entity holds the position or role of king in relation to another entity, typically a territory, people, or domain.
-
B.
alsoKingOf
Indicates that an entity who is king of one place is simultaneously king of another place as well.
-
C.
fatherIsRulerOf
Indicates that the person who is the father holds the position of ruler or sovereign over the specified entity or domain.
-
D.
kingPowers
Indicates that an entity possesses the legal or authoritative powers associated with a king over another entity or domain.
-
E.
仕えた君主
Indicates a relationship where someone served or was in the service of a particular lord or sovereign.
- F. None of above. chosen
Provenance (4 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_69efd6b156448190bfa15958208395c3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f641eae0dc81909c82bc2119305b03 |
completed | May 2, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 27, 2026, 10:05 p.m.