Triple
T26618950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honey Best |
E668139
|
entity |
| Predicate | appearsPrimarilyAs |
P94931
|
FINISHED |
| Object | off-screen character |
—
|
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: off-screen character | Statement: [Honey Best, appearsPrimarilyAs, off-screen character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsPrimarilyAs Context triple: [Honey Best, appearsPrimarilyAs, off-screen character]
-
A.
appearsAs
Indicates that one entity is presented, perceived, or manifested in the form, role, or guise of another entity.
-
B.
firstAppearsAs
Indicates that an entity is introduced or shown in a particular form, role, or identity for the first time in a given context.
-
C.
existsPrimarilyAs
chosen
Indicates that one entity’s main or fundamental mode of being or manifestation is in the form of another specified entity or state.
-
D.
primarilyRepresentedBy
Indicates that one entity serves as the main or most characteristic representation or depiction of another entity.
-
E.
performsPrimarilyIn
Indicates that an entity (such as a performer or group) mainly carries out its performances within a particular location, medium, or 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_69ee9cfe16088190a3dddd68e3c7b1ea |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 27, 2026, 2:20 a.m.