Triple
T26567233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Burnell |
E666718
|
entity |
| Predicate | honourHeldBy |
P108644
|
FINISHED |
| Object | Edward Smith-Stanley, 12th Earl of Derby |
E176765
|
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: Edward Smith-Stanley, 12th Earl of Derby | Statement: [Baron Burnell, honourHeldBy, Edward Smith-Stanley, 12th Earl of Derby]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honourHeldBy Context triple: [Baron Burnell, honourHeldBy, Edward Smith-Stanley, 12th Earl of Derby]
-
A.
honourOf
Indicates that one entity is the source, bearer, or cause of another entity’s honor, prestige, or distinguished recognition.
-
B.
honoursHolder
chosen
Indicates that one entity is the designated recipient or bearer of a particular honour, award, or distinction conferred by another entity.
-
C.
honoursTitleHolder
Indicates that one entity formally recognizes and pays respect to another entity that holds a particular title or honor.
-
D.
honourType
Indicates the specific category or classification of an honour or award associated with an entity.
-
E.
honoredOn
Indicates that an entity is formally recognized, celebrated, or commemorated on a specific date or occasion.
- F. None of above.
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_69ee9cfa21c081909e4e36e087debfc6 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f614a0c2408190b494a3d1f624c042 |
completed | May 2, 2026, 3:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a15e67eb9bc8190a5e6580f1043e402 |
completed | May 26, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:55 a.m.