Triple
T34640328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elvenking |
E889537
|
entity |
| Predicate | appearsAsCharacter |
P192578
|
FINISHED |
| Object | Elvenking (The Hobbit) |
—
|
NE NERFINISHED |
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: Elvenking (The Hobbit) | Statement: [Elvenking, appearsAsCharacter, Elvenking (The Hobbit)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsAsCharacter Context triple: [Elvenking, appearsAsCharacter, Elvenking (The Hobbit)]
-
A.
appearsWithCharacter
Indicates that two characters are shown or present together within the same scene, shot, or context.
-
B.
appearsInFictionAs
chosen
Indicates that one entity is depicted or represented as a character, figure, or element within a fictional work or narrative.
-
C.
characterAppearsIn
Indicates that a specific character is present or featured within a particular work, such as a book, movie, or episode.
-
D.
cameoCharacter
Indicates that one entity appears briefly or in a minor, special-guest role within the context or work associated with another entity.
-
E.
appearsAgainst
Indicates that one entity is visually or publicly presented in opposition to, or in contrast with, another entity.
- 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_69f349d724848190b63ad3407e0006d9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fdee770af48190aca2670db50f8b49 |
completed | May 8, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69fdecec98a08190a357d816dc2a6dbe |
completed | May 8, 2026, 2:02 p.m. |
Created at: May 1, 2026, 2:04 a.m.