Triple
T37216254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Jengland |
E922743
|
entity |
| Predicate | recognizedTitleGrantedTo |
P168
|
FINISHED |
| Object | Erispoe |
—
|
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: Erispoe | Statement: [Battle of Jengland, recognizedTitleGrantedTo, Erispoe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizedTitleGrantedTo Context triple: [Battle of Jengland, recognizedTitleGrantedTo, Erispoe]
-
A.
recognizedTitleHolder
Indicates that an entity is officially acknowledged as holding a particular title or position.
-
B.
authorizedByTitle
Indicates that an action or permission is granted based on a person’s role, position, or formal title rather than on individual identity.
-
C.
grantedTo
chosen
Indicates that a right, permission, or resource has been formally given or assigned by one party to another.
-
D.
grantedRecognitionBy
Indicates that an entity has been formally acknowledged, honored, or validated by another entity.
-
E.
grantedBy
Indicates that a right, permission, or benefit is conferred or authorized by one entity to another.
- 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_69f76ea6f5288190b8d9988f613811c0 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
Created at: May 3, 2026, 4:15 p.m.