Triple
T30464837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miss Mouse |
E775105
|
entity |
| Predicate | oftenAccompaniedByCharacter |
P3100
|
FINISHED |
| Object | Uncle Rat |
—
|
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: Uncle Rat | Statement: [Miss Mouse, oftenAccompaniedByCharacter, Uncle Rat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenAccompaniedByCharacter Context triple: [Miss Mouse, oftenAccompaniedByCharacter, Uncle Rat]
-
A.
oftenAccompaniedBy
chosen
Indicates that one entity is frequently found together with, occurs alongside, or is commonly associated in presence or use with another entity.
-
B.
usuallyAccompaniedBy
Indicates that one entity is commonly or habitually found together with, or occurs in the presence of, another entity.
-
C.
attendedByFictionalCharacter
Indicates that a fictional character is present at, participates in, or is an attendee of a particular event or gathering.
-
D.
supportingCharacter
Indicates that one entity plays a secondary or assisting role in the story or context relative to another primary entity.
-
E.
companionOf
Indicates that one entity serves as a companion or partner to another, typically accompanying or being closely associated with them.
- 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_69f2249622a48190b1fae2e3e4ee958a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: April 29, 2026, 8:11 p.m.