Triple
T9535380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Demetrius |
E230000
|
entity |
| Predicate | commendedBy |
P88588
|
FINISHED |
| Object | author of 3 John |
—
|
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: author of 3 John | Statement: [Demetrius, commendedBy, author of 3 John]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commendedBy Context triple: [Demetrius, commendedBy, author of 3 John]
-
A.
commendedFor
Indicates that one entity has expressed praise or approval toward another entity specifically because of a particular action, quality, or achievement.
-
B.
recommendedIn
Indicates that one entity is suggested or endorsed within the context, content, or scope of another entity (such as a document, list, or recommendation source).
-
C.
implementsRecommendationOf
Indicates that one entity carries out or puts into practice a recommendation that was proposed or issued by another entity.
-
D.
submitsRecommendationsTo
Indicates that one entity formally sends or presents recommendations to another entity for consideration or action.
-
E.
madeRecommendation
Indicates that one entity has suggested or advised another entity to consider a particular option, action, or choice.
- 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_69ca847b1b3081908f72bc932c17cc41 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd98cc58bc8190ba921410e4b64aaa |
completed | April 1, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69cca56c44f88190a54a5d2a133bb07e |
completed | April 1, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69cca89f1d748190bf3636bea28d8a37 |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 8 p.m.