Triple
T36840603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Consolations of Scholarship |
E910394
|
entity |
| Predicate | usesTextSetting |
P192953
|
FINISHED |
| Object | prominent |
—
|
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: prominent | Statement: [The Consolations of Scholarship, usesTextSetting, prominent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTextSetting Context triple: [The Consolations of Scholarship, usesTextSetting, prominent]
-
A.
usesTextService
Indicates that an entity makes use of a text-based service to perform some function or obtain some benefit.
-
B.
usesTextBy
Indicates that one entity makes use of or relies on a text authored or provided by another entity.
-
C.
useText
Indicates that one entity employs or applies a specific text as a resource, tool, or content in performing an action or fulfilling a function.
-
D.
hasTypeOfTextSetting
Indicates that an entity is associated with a particular configuration or style that determines how its text is presented or formatted.
-
E.
allowsText
Indicates that one entity permits or supports the use, input, or display of textual content in relation to 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_69f76e7f65a881908651b702da592b6d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69fd328298ac8190b6bd5ded7dca270d |
completed | May 8, 2026, 12:46 a.m. |
Created at: May 3, 2026, 4:13 p.m.