Triple
T18643613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bumble |
E455749
|
entity |
| Predicate | developer |
P73
|
FINISHED |
| Object | Bumble Inc. |
—
|
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: Bumble Inc. | Statement: [Bumble, developer, Bumble Inc.]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bumble Inc. Context triple: [Bumble, developer, Bumble Inc.]
-
A.
Bumble
chosen
Bumble is a popular dating and social networking app known for its women-first messaging approach and focus on empowering respectful connections.
-
B.
Bumble Bee
"Bumble Bee" is a classic blues song by Memphis Minnie, recognized as one of her most enduring and influential recordings.
-
C.
Bumble Bee
Bumble Bee is a historic Old West ghost town in Arizona that once served as a stagecoach stop and mining community.
-
D.
Bee Network
Bee Network is Greater Manchester’s integrated public transport system brand, unifying buses, trams, cycling and walking under a single, coordinated network.
-
E.
Buzzr
Buzzr is an American digital multicast television network specializing in classic game shows from the mid-20th century onward.
- 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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5500b6d7c8190b807b772980d913c |
completed | April 19, 2026, 9:58 p.m. |
Created at: April 10, 2026, 11:47 a.m.