Triple
T12885025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Junky |
E308203
|
entity |
| Predicate | protagonistSharesNameWithAuthor |
P107446
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Junky, protagonistSharesNameWithAuthor, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistSharesNameWithAuthor Context triple: [Junky, protagonistSharesNameWithAuthor, true]
-
A.
protagonistAlsoKnownAs
Indicates that an entity serving as a protagonist is alternatively referred to by another name or alias.
-
B.
protagonistFullName
Indicates that the subject entity is the full, proper name (including given and family names) of the story’s main protagonist.
-
C.
protagonistIs
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative context.
-
D.
protagonistNationality
Indicates the country or national identity to which the protagonist of a work is associated or belongs.
-
E.
protagonistBasedOn
Indicates that a fictional work’s main character is modeled on, inspired by, or derived from a particular real or fictional person or 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97c7f91d08190aac2f6419d3ba992 |
completed | April 10, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69d96fa55b888190ab1612e93c41aec4 |
completed | April 10, 2026, 9:46 p.m. |
| PDg | Predicate description generation | batch_69d97c7d0598819080cab0a2314bc106 |
completed | April 10, 2026, 10:41 p.m. |
Created at: April 9, 2026, 5:39 p.m.