Triple
T10959207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Most Honourable |
E258923
|
entity |
| Predicate | followsName |
P9013
|
FINISHED |
| Object | personal name of the honouree |
—
|
LITERAL 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: personal name of the honouree | Statement: [The Most Honourable, followsName, personal name of the honouree]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsName Context triple: [The Most Honourable, followsName, personal name of the honouree]
-
A.
followsNameOf
chosen
Indicates that one entity’s name comes immediately after another entity’s name in a specified ordering or sequence.
-
B.
followsBy
Indicates that one event, state, or entity occurs or comes immediately after another in a sequence or order.
-
C.
followsTo
Indicates that one entity moves or proceeds behind another entity toward a specific destination or target.
-
D.
follows
Indicates that one entity comes after, moves behind, or acts in accordance with another entity in time, space, or sequence.
-
E.
followsBetween
Indicates that one entity comes after or succeeds another entity within a specified context or sequence.
- 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_69d6aa88500c819097d7032ca578e74f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d77127b10481908ad1efafb2a338d1 |
completed | April 9, 2026, 9:28 a.m. |
| PD | Predicate disambiguation | batch_69d72e874f48819096ffa878f90c7d5b |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:23 p.m.