Triple
T22840334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Girlfriends' Guide to Divorce |
E566062
|
entity |
| Predicate | network |
P2637
|
FINISHED |
| Object | Bravo |
—
|
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: Bravo | Statement: [Girlfriends' Guide to Divorce, network, Bravo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bravo Context triple: [Girlfriends' Guide to Divorce, network, Bravo]
-
A.
Bravo
Bravo is a company best known for operating the Bravo app, a platform that facilitates cashless tipping and payments.
-
B.
Bravo
chosen
Bravo is an American cable television network best known for its reality TV programming and pop culture–focused entertainment.
-
C.
Brava
Brava is a small, mountainous island in the Cape Verde archipelago known for its lush vegetation, volcanic landscapes, and traditional Creole culture.
-
D.
Brava
Brava is a coastal city in southern Somalia known for its historic Swahili-Arabic cultural heritage and role as a regional trading center on the Indian Ocean.
-
E.
Bravos
Bravos is the popular nickname of FC Juárez, a professional football club based in Ciudad Juárez, Mexico.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e245869e188190a196584f36e682da |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17e83fa48819084568264ef45c833 |
completed | April 29, 2026, 3:44 a.m. |
Created at: April 17, 2026, 3:35 p.m.