Triple
T16812971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Tough Mind and a Tender Heart |
E408660
|
entity |
| Predicate | widelyCitedIn |
P60904
|
FINISHED |
| Object | theology |
—
|
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: theology | Statement: [A Tough Mind and a Tender Heart, widelyCitedIn, theology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: widelyCitedIn Context triple: [A Tough Mind and a Tender Heart, widelyCitedIn, theology]
-
A.
oftenCitedAs
chosen
Indicates that one entity is frequently referenced or mentioned as an example, source, or authority in relation to another entity.
-
B.
isCitedFor
Indicates that one entity references another as a source of information, evidence, or authority for a specific claim, idea, or contribution.
-
C.
citesAs
Indicates that one entity references or acknowledges another as a source of information, authority, or evidence.
-
D.
usedAsAuthorCitationFor
Indicates that one entity is cited or referenced as the author in the bibliographic citation of another entity.
-
E.
citationOf
Indicates that one entity cites, references, or formally acknowledges another entity as a source.
- 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b2df5c888190a462614e1432c357 |
completed | April 18, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69e32b814b188190aee525f8779203cd |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.