Triple
T24304793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edgar the Peaceful |
E612503
|
entity |
| Predicate | honorificEpitet |
P155486
|
FINISHED |
| Object | the Peaceful |
—
|
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: the Peaceful | Statement: [Edgar the Peaceful, honorificEpitet, the Peaceful]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorificEpitet Context triple: [Edgar the Peaceful, honorificEpitet, the Peaceful]
-
A.
honorificEponym
Indicates that one entity serves as an honorific namesake for another, typically recognizing or commemorating the person or entity in whose honor something is named.
-
B.
honorificSense
Indicates that one entity refers to another using an honorific or respectful linguistic form.
-
C.
honorificNature
Indicates that the relationship involves the use or assignment of an honorific title or respectful form of address between entities.
-
D.
honorificIndicates
Indicates that one entity uses an honorific title or respectful form of address to refer to or address another entity.
-
E.
honorificNickname
Indicates that one entity is referred to by a respectful or honorific nickname by another entity or in a given context.
- 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_69e2d7d91bb48190bc5377d17a85fb21 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2922641bc81908fa3595941e60741 |
completed | April 29, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69f1c45c6ec081908401b69424428100 |
completed | April 29, 2026, 8:42 a.m. |
| PDg | Predicate description generation | batch_69f1c6d4e99081909f61899eccafb73e |
completed | April 29, 2026, 8:52 a.m. |
Created at: April 18, 2026, 1:30 a.m.