Triple
T26543483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Houston family |
E671453
|
entity |
| Predicate | hasOnScreenRepresentation |
P103
|
FINISHED |
| Object | “Being Bobby Brown” |
—
|
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: “Being Bobby Brown” | Statement: [Houston family, hasOnScreenRepresentation, “Being Bobby Brown”]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnScreenRepresentation Context triple: [Houston family, hasOnScreenRepresentation, “Being Bobby Brown”]
-
A.
hasOnscreenFunction
Indicates that an entity serves a particular role or performs a specific function when it appears on screen.
-
B.
hasOnScreenText
Indicates that some text content is visually displayed on a screen within a given context or medium.
-
C.
hasOnScreenRelative
Indicates that one entity has a family member who appears or is depicted on screen in relation to it.
-
D.
hasRepresentationIn
chosen
Indicates that one entity is represented, depicted, or encoded within another entity, such as a concept, object, or data structure having a corresponding representation in a specific medium or context.
-
E.
hasOnScreenOwner
Indicates that an entity is owned or controlled by another entity that is explicitly shown or represented on screen.
- 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_69eeb3206e748190b90c85cc81f38c91 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 1:43 a.m.