Triple
T24202541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bobby Lashley |
E600018
|
entity |
| Predicate | formedStable |
P155163
|
FINISHED |
| Object | The Hurt Business |
—
|
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: The Hurt Business | Statement: [Bobby Lashley, formedStable, The Hurt Business]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedStable Context triple: [Bobby Lashley, formedStable, The Hurt Business]
-
A.
formed
Indicates that one entity came into existence, shape, or organization as a result of the actions or processes involving another entity.
-
B.
formedState
Indicates that an entity brought a particular state, condition, or configuration into existence or caused it to come about.
-
C.
formedInState
Indicates that an entity was created, established, or officially organized within a particular state or subnational jurisdiction.
-
D.
formedTo
Indicates that one entity was created, established, or organized for the purpose of serving, supporting, or enabling another entity or activity.
-
E.
formedWithin
Indicates that one entity was created, established, or came into existence inside the spatial or structural bounds 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_69e288ceaab88190899d0acb5931591d |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27ca2d6708190ba20d00870d0af49 |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f1c9834064819082024233d9c6f98f |
completed | April 29, 2026, 9:04 a.m. |
Created at: April 17, 2026, 11:36 p.m.