Triple
T36997112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alfredian law code |
E915258
|
entity |
| Predicate | hasPrologueAuthor |
P205687
|
FINISHED |
| Object | Alfred the Great |
E22387
|
NE 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: Alfred the Great | Statement: [Alfredian law code, hasPrologueAuthor, Alfred the Great]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrologueAuthor Context triple: [Alfredian law code, hasPrologueAuthor, Alfred the Great]
-
A.
hasPrologueCharacter
Indicates that a character appears or is involved in the prologue section of a narrative work.
-
B.
hasPrologueSometimes
Indicates that an entity occasionally or in some instances includes a prologue.
-
C.
hasPrologueInTitle
Indicates that a work’s title explicitly includes the word “Prologue” or a prologue-related phrase.
-
D.
hasPrologueSeries
Indicates that one work serves as a prologue or introductory installment to another work in a series.
-
E.
hasPrologueSetting
Indicates that the setting specified is the location or context in which the prologue of a work takes place.
- F. None of above. chosen
Provenance (5 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_69f76e8f1a8c81909db172ed31304971 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3efdae405481909c4896c31b4adb27 |
completed | June 26, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:14 p.m.