Triple
T16117456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Reverend |
E391040
|
entity |
| Predicate | addressedBefore |
P121541
|
FINISHED |
| Object | personal name |
—
|
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 | Statement: [The Reverend, addressedBefore, personal name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addressedBefore Context triple: [The Reverend, addressedBefore, personal name]
-
A.
addressedBy
Indicates that something (such as an issue, request, or item) is handled, dealt with, or responded to by a particular agent or entity.
-
B.
addressedThrough
Indicates that an issue, request, or communication is handled, resolved, or processed by means of a specified channel, method, or intermediary.
-
C.
spokenBefore
Indicates that one entity has spoken or produced speech earlier in time than another entity.
-
D.
isAddressedTo
Indicates that a message, communication, or item is specifically directed or intended for a particular recipient.
-
E.
usedBefore
Indicates that one entity was utilized or applied prior to the use or occurrence of another entity.
- 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2016c10a081909b2d23ecea153a9c |
completed | April 17, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e1828518c48190a8ef3aaa46a1f639 |
completed | April 17, 2026, 12:44 a.m. |
| PDg | Predicate description generation | batch_69e183b9d3f08190953ada68f4272996 |
completed | April 17, 2026, 12:50 a.m. |
Created at: April 10, 2026, 5 a.m.