Triple
T20358527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De nobilitate |
E496713
|
entity |
| Predicate | discourseType |
P139815
|
FINISHED |
| Object | moral and social critique |
—
|
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: moral and social critique | Statement: [De nobilitate, discourseType, moral and social critique]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discourseType Context triple: [De nobilitate, discourseType, moral and social critique]
-
A.
discourse
Indicates that one entity engages in extended verbal or written communication or discussion with another entity.
-
B.
typeOfForum
Indicates the specific category or kind of forum that an entity belongs to or is classified as.
-
C.
discussionPublic
Indicates that a discussion is accessible to the general public rather than being restricted or private.
-
D.
dialogueType
Indicates the specific kind or category of dialogue occurring between entities (e.g., question-answer, negotiation, instruction).
-
E.
discussedAs
Indicates that one entity is talked about, treated, or examined in terms of another entity, often as an example, case, or framing concept.
- 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_69e0b4a3f7f48190b37f354574028ca6 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67855c3a88190b88839a47d01184d |
completed | April 20, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69e57636b4808190bc2855af48a3ccdc |
completed | April 20, 2026, 12:41 a.m. |
| PDg | Predicate description generation | batch_69e58d7481508190a87c8b88f9df9879 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:25 a.m.