Triple
T30788688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eddie (Da 5 Bloods) |
E784027
|
entity |
| Predicate | associatedWithCharacterGroupName |
P47706
|
FINISHED |
| Object | Da 5 Bloods |
E42175
|
NE FINISHED |
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: Da 5 Bloods | Statement: [Eddie (Da 5 Bloods), associatedWithCharacterGroupName, Da 5 Bloods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithCharacterGroupName Context triple: [Eddie (Da 5 Bloods), associatedWithCharacterGroupName, Da 5 Bloods]
-
A.
associatedWithCharacterGroup
chosen
Indicates that an entity has a connection or affiliation with a particular group of characters.
-
B.
associatedWithCharacterFamily
Indicates a relationship where something is linked or connected to a particular character’s family.
-
C.
associatedWithCharacterAlias
Indicates that one entity is linked to or connected with an alternative name or alias used for a particular character.
-
D.
associatedWithCharacterRole
Indicates that one entity has a connection or linkage to a specific character role played or held by another entity.
-
E.
belongsToCharacter
Indicates that something is owned, associated with, or under the domain of a particular character.
- F. None of above.
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_69f224b2e2a48190b19aa43db9da5b67 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a28fb9941f081909002bcd2ced66753 |
completed | June 10, 2026, 5:52 a.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:41 p.m.