Triple
T17906213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bunny Bravo |
E447706
|
entity |
| Predicate | homeLife |
P4085
|
FINISHED |
| Object | lives with her adult son Johnny Bravo |
—
|
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: lives with her adult son Johnny Bravo | Statement: [Bunny Bravo, homeLife, lives with her adult son Johnny Bravo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeLife Context triple: [Bunny Bravo, homeLife, lives with her adult son Johnny Bravo]
-
A.
homeLifeDescription
Indicates a description of an entity’s domestic or everyday living situation and conditions.
-
B.
household
chosen
Indicates that two or more entities belong to or are part of the same household unit, typically sharing a residence and domestic life.
-
C.
homeFront
Indicates a relationship where an entity is associated with the domestic sphere or civilian side of a conflict, typically supporting war efforts away from the battlefield.
-
D.
homeManager
Indicates that one entity manages, oversees, or is responsible for the operations or affairs of another entity’s home or household.
-
E.
houseUse
Indicates how a house or dwelling is used or purposed (e.g., residential, commercial, mixed-use).
- 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_69d8b9f6d394819082a6d69fd1e23d2f |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49e9c7f54819088c6d2ce7bbea073 |
completed | April 19, 2026, 9:21 a.m. |
| PD | Predicate disambiguation | batch_69e3d8ec2f6881909d7f54b878cbed37 |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:19 a.m.