Triple
T20984006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salanio |
E516844
|
entity |
| Predicate | providesExpositionAbout |
P142360
|
FINISHED |
| Object | Antonio’s sadness |
—
|
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: Antonio’s sadness | Statement: [Salanio, providesExpositionAbout, Antonio’s sadness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesExpositionAbout Context triple: [Salanio, providesExpositionAbout, Antonio’s sadness]
-
A.
expositionMode
Indicates the manner or format in which information, narrative, or content is presented or explained.
-
B.
providesExposureTo
Indicates that one entity gives another entity the opportunity to be seen, noticed, or become known by a particular audience, environment, or set of influences.
-
C.
expositionPurpose
Indicates that something (such as a text, speech, or display) serves the purpose of explaining, clarifying, or providing background information about a subject.
-
D.
exposes
Indicates making something visible, known, or vulnerable by removing cover, concealment, or protection.
-
E.
expositionOfficialName
Indicates the officially designated name under which an exposition is formally recognized or presented.
- 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_69e0b4ffac148190bbade9f0eceb660b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fbe1474c8190912b90da0973f99f |
completed | April 21, 2026, 4:24 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2df1a888190b5b478e76bdf7fdf |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 1:48 p.m.