Triple
T32124331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trixie |
E820457
|
entity |
| Predicate | appearsMostlyAt |
P55519
|
FINISHED |
| Object | Bonnie Anderson's home |
—
|
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: Bonnie Anderson's home | Statement: [Trixie, appearsMostlyAt, Bonnie Anderson's home]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsMostlyAt Context triple: [Trixie, appearsMostlyAt, Bonnie Anderson's home]
-
A.
primaryLocationOfAppearances
chosen
Indicates the main place where an entity most frequently appears or is featured.
-
B.
appearsIn
Indicates that an entity is present, featured, or occurs within a particular context, work, or medium.
-
C.
mayAppearOn
Indicates that one entity is allowed or able to be shown, featured, or present on another entity (such as a platform, medium, or surface).
-
D.
appearsFor
Indicates that one entity is presented, shown, or made visible on behalf of, or in representation of, another entity.
-
E.
occasionallyPlaysAt
Indicates that an entity performs or participates in an activity at a particular place or context from time to time, but not regularly or frequently.
- 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_69f34902d42c819083a8e6bba9a8bb9a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: May 1, 2026, 12:29 a.m.