Triple
T27175366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Adventures of a Nobody |
E683028
|
entity |
| Predicate | impliedTheme |
P159080
|
FINISHED |
| Object | social invisibility |
—
|
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: social invisibility | Statement: [The Adventures of a Nobody, impliedTheme, social invisibility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impliedTheme Context triple: [The Adventures of a Nobody, impliedTheme, social invisibility]
-
A.
impliesTheme
chosen
Indicates that one entity conceptually suggests, hints at, or leads to the thematic presence of another entity.
-
B.
theme
Indicates the entity that is the primary participant or content affected or characterized by an action, event, or state.
-
C.
themeFor
Indicates that something serves as the central subject, topic, or focus for another thing (such as an event, work, or activity).
-
D.
usesThemeBy
Indicates that one entity incorporates, applies, or is based on a theme that was created, defined, or provided by another entity.
-
E.
subjectImpliedAs
Indicates that the subject of an action or statement is not explicitly stated but is understood or inferred from context.
- 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_69eefad086808190ab89816c0c300476 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f62cd2ceb481908cd9fae52a542206 |
completed | May 2, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 9:25 a.m.