Triple
T4620618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of the English |
E100969
|
entity |
| Predicate | titleHoldersCollectively |
P57464
|
FINISHED |
| Object | Anglo-Saxon kings of England |
—
|
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: Anglo-Saxon kings of England | Statement: [King of the English, titleHoldersCollectively, Anglo-Saxon kings of England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleHoldersCollectively Context triple: [King of the English, titleHoldersCollectively, Anglo-Saxon kings of England]
-
A.
titleHolderIs
Indicates that one entity currently holds or possesses a specific title associated with another entity.
-
B.
titleHolderName
Indicates the name of the person or entity that holds a particular title or position.
-
C.
titleHolderIsUsually
Indicates that an entity serving as a title holder is typically or most commonly a particular type or category of entity.
-
D.
titleHolderTo
Indicates that one entity currently holds or possesses an official title, position, or designation in relation to another entity.
-
E.
titleHolderType
Indicates the specific role or capacity in which an entity holds a title (e.g., owner, trustee, beneficiary).
- 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59e560f481908abb1a97b4ff5795 |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd5231db7c8190b38d4fdbad8bf842 |
completed | March 20, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69bd56b5f4648190834eafa666d53caa |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:12 p.m.