Triple
T1433253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theophilus |
E30497
|
entity |
| Predicate | honorificTitleUsed |
P2097
|
FINISHED |
| Object | most excellent |
—
|
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: most excellent | Statement: [Theophilus, honorificTitleUsed, most excellent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorificTitleUsed Context triple: [Theophilus, honorificTitleUsed, most excellent]
-
A.
honorificTitle
chosen
Indicates that one entity serves as a formal honorific or respectful title used to address or refer to another entity.
-
B.
honorificType
Indicates the type or category of honorific or formal title associated with an entity in a given context.
-
C.
honorificPrefix
Indicates the formal title or respectful prefix (e.g., "Dr.", "Mr.", "Prof.") used before a person's name to denote status, role, or honor.
-
D.
hasHonorificName
Indicates that an entity is referred to by a formal or respectful title or name used as an honorific.
-
E.
honorificSuffix
Indicates that one entity is a respectful or formal suffix appended to another entity’s name or title.
- 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_69a498fc69ec8190b61722bd4b67c4d2 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c500a9888190a16fbb1ec97a79c9 |
completed | March 1, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69a4c4771c9481908ae47c959debbe77 |
completed | March 1, 2026, 10:57 p.m. |
Created at: March 1, 2026, 8 p.m.