Triple
T32778047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beornwulf of Mercia |
E838271
|
entity |
| Predicate | recordInSource |
P193371
|
FINISHED |
| Object | Anglo-Saxon Chronicle |
—
|
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: Anglo-Saxon Chronicle | Statement: [Beornwulf of Mercia, recordInSource, Anglo-Saxon Chronicle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordInSource Context triple: [Beornwulf of Mercia, recordInSource, Anglo-Saxon Chronicle]
-
A.
recorded
Indicates that one entity captured, stored, or documented information, audio, video, or data about another entity or event.
-
B.
reRecordedFrom
Indicates that one recording is a new recording derived from, based on, or made again from an earlier recording.
-
C.
recordingOf
Indicates that one entity is an audio or video capture or performance that documents, represents, or preserves another entity (such as a work, event, or expression).
-
D.
recordEvent
Indicates that an entity logs or stores information about a specific occurrence or action as an event.
-
E.
recordingFor
Indicates that one entity serves as a recorded representation (such as audio, video, or data capture) created for, or documenting, another entity or event.
- 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_69f3493a824c8190938489ba69041d08 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69fd4445f8c08190bb2dc27e0971c55d |
completed | May 8, 2026, 2:02 a.m. |
Created at: May 1, 2026, 1:13 a.m.