Triple
T27175371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Adventures of a Nobody |
E683028
|
entity |
| Predicate | centralCharacterDescription |
P32702
|
FINISHED |
| Object | unremarkable |
—
|
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: unremarkable | Statement: [The Adventures of a Nobody, centralCharacterDescription, unremarkable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralCharacterDescription Context triple: [The Adventures of a Nobody, centralCharacterDescription, unremarkable]
-
A.
protagonistDescription
Indicates that a text provides a descriptive summary or characterization of the story’s main protagonist.
-
B.
narrativeCharacter
Indicates that one entity functions as a character within the narrative or story associated with another entity.
-
C.
characterDescription
chosen
Indicates that one entity provides a textual description or portrayal of the characteristics, traits, or attributes of another entity.
-
D.
character1
Indicates that the subject is identified as the first or primary character in a narrative or context.
-
E.
mainProtagonist
Indicates that the subject is the central character or primary focus in the narrative of the related work.
- 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_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 27, 2026, 9:25 a.m.