Triple
T30788684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eddie (Da 5 Bloods) |
E784027
|
entity |
| Predicate | countryOfServiceInBackstory |
P40676
|
FINISHED |
| Object | United States |
—
|
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: United States | Statement: [Eddie (Da 5 Bloods), countryOfServiceInBackstory, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryOfServiceInBackstory Context triple: [Eddie (Da 5 Bloods), countryOfServiceInBackstory, United States]
-
A.
countryOfMilitaryService
chosen
Indicates that an entity served or is serving in the armed forces of a specified country.
-
B.
placeOfMilitaryService
Indicates the location or institution where a person performed their military service.
-
C.
fictionalCountryOfService
Indicates that an entity served (e.g., worked, was stationed, or held office) in a country that is fictional rather than real.
-
D.
branchOfServiceInBackstory
Indicates that an entity’s backstory includes service in a specified military or organizational branch.
-
E.
militaryUnitTypeServed
Indicates that an entity served in, or was a member of, a specific type of military unit.
- 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_69ffacdf9f5c8190baef0245edfe87fc |
completed | May 9, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69ffac5e86e08190a1e6da0840a237ad |
completed | May 9, 2026, 9:51 p.m. |
Created at: April 29, 2026, 8:41 p.m.