Triple
T3147636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bravo |
E65800
|
entity |
| Predicate | programmingTheme |
P25955
|
FINISHED |
| Object | celebrity culture |
—
|
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: celebrity culture | Statement: [Bravo, programmingTheme, celebrity culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programmingTheme Context triple: [Bravo, programmingTheme, celebrity culture]
-
A.
programming
Indicates that an entity writes, develops, or modifies software or code, typically using a programming language to create or control computer programs.
-
B.
programmingLanguage
Indicates that one entity is a programming language used to create, control, or interact with the other entity.
-
C.
programmingFocus
Indicates a relationship where an entity’s primary attention, effort, or specialization is directed toward a particular area or aspect of programming.
-
D.
themeFor
chosen
Indicates that something serves as the central subject, topic, or focus for another thing (such as an event, work, or activity).
-
E.
programmingIncludes
Indicates that one programming-related entity contains, incorporates, or makes use of another as a part, feature, or component.
- 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_69ad8584485081909ed529e890cadc4a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada59a54188190a2e020fd4004d734 |
completed | March 8, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfa3d9081908425aa636bb9b897 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:05 p.m.