Triple
T31819694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HP-71B |
E812225
|
entity |
| Predicate | displayCharacters |
P64394
|
FINISHED |
| Object | 22-character display |
—
|
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: 22-character display | Statement: [HP-71B, displayCharacters, 22-character display]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: displayCharacters Context triple: [HP-71B, displayCharacters, 22-character display]
-
A.
featuresCharactersFrom
Indicates that one entity (such as a work or production) includes or presents characters originating from another entity.
-
B.
BBCCharacterPage
Indicates that there exists a BBC web page specifically dedicated to providing information about the character.
-
C.
screenCharacterBy
Indicates a relationship where one entity evaluates or selects characters according to certain criteria or standards.
-
D.
characterDisplay
chosen
Indicates a relationship where one entity visually presents or renders the appearance or representation of a character or set of characters.
-
E.
characterIn
Indicates that an entity appears as a character within a specified work, story, or narrative.
- 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_69f348e97fa48190aa06286962af6dee |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6af7f24a881909e6ae0d937e90ea2 |
completed | May 3, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:45 p.m.