Triple
T37396462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Namond Brice |
E928865
|
entity |
| Predicate | friendshipGroup |
P34598
|
FINISHED |
| Object | middle school boys in West Baltimore |
—
|
LITERAL 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: middle school boys in West Baltimore | Statement: [Namond Brice, friendshipGroup, middle school boys in West Baltimore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: friendshipGroup Context triple: [Namond Brice, friendshipGroup, middle school boys in West Baltimore]
-
A.
friendGroupRole
Indicates the specific role or function an individual holds within a particular friend group.
-
B.
hasFriendGroupName
Indicates that an entity is associated with a friend group identified by a specific name.
-
C.
groups
Indicates that one entity organizes, clusters, or associates multiple entities together as members of a collective set or category.
-
D.
formedGroup
Indicates that multiple entities have come together to create or establish a group or collective unit.
-
E.
hasSocialGroup
chosen
Indicates that an entity belongs to, is associated with, or participates in a particular social group or community.
- 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_69f76ebb10c481909b54b9dba263e29f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:16 p.m.