Triple
T27936163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bubba Blue |
E700616
|
entity |
| Predicate | businessPlanWith |
P166859
|
FINISHED |
| Object | Forrest Gump |
—
|
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: Forrest Gump | Statement: [Bubba Blue, businessPlanWith, Forrest Gump]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: businessPlanWith Context triple: [Bubba Blue, businessPlanWith, Forrest Gump]
-
A.
businessPlanSubject
Indicates that one entity is the subject or main focus of a business plan associated with another entity.
-
B.
businessStrategy
Indicates the overarching plan or approach an entity adopts to achieve its business goals, compete in its market, and allocate resources.
-
C.
businessVenture
Indicates a relationship where entities jointly engage in, operate, or are involved with a commercial or entrepreneurial undertaking.
-
D.
businessGeneration
Indicates that one entity is responsible for creating, initiating, or driving new business opportunities, revenue, or commercial activity for another entity.
-
E.
businessName
Indicates that one entity is the official or recognized business name of another entity.
- F. None of above. chosen
Provenance (4 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_69ef6a5028108190a14696d9821dde49 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f664aa283c8190a869d0555eff60c6 |
completed | May 2, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f6645a615481909b53d94512ecbaf1 |
completed | May 2, 2026, 8:53 p.m. |
Created at: April 27, 2026, 7:13 p.m.