Triple
T30788692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eddie (Da 5 Bloods) |
E784027
|
entity |
| Predicate | hasFormerSquadLeader |
P7716
|
FINISHED |
| Object | Norman (Da 5 Bloods) |
—
|
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: Norman (Da 5 Bloods) | Statement: [Eddie (Da 5 Bloods), hasFormerSquadLeader, Norman (Da 5 Bloods)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerSquadLeader Context triple: [Eddie (Da 5 Bloods), hasFormerSquadLeader, Norman (Da 5 Bloods)]
-
A.
hasFormerLeader
chosen
Indicates that an entity previously held the role of leader of another entity but no longer does.
-
B.
wasLeaderOnTeam
Indicates that a person held a leadership role on a particular team.
-
C.
wasInSquadFor
Indicates that an individual was a member of a particular squad or team, typically for a specific event, period, or organization.
-
D.
hasFormerTeam
Indicates that an entity was previously a member of, played for, or was affiliated with a team in the past but is no longer associated with that team.
-
E.
servedAsCaptainFrom
Indicates that an entity held the role of captain of another entity starting from a specified point in time.
- 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_69f224b2e2a48190b19aa43db9da5b67 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
Created at: April 29, 2026, 8:41 p.m.