Triple
T4967000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baltimore Claws |
E111552
|
entity |
| Predicate | proposedNameRejectedBecause |
P37898
|
FINISHED |
| Object | negative connotations of 'Hustlers' |
—
|
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: negative connotations of 'Hustlers' | Statement: [Baltimore Claws, proposedNameRejectedBecause, negative connotations of 'Hustlers']
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposedNameRejectedBecause Context triple: [Baltimore Claws, proposedNameRejectedBecause, negative connotations of 'Hustlers']
-
A.
rejectedBy
Indicates that one entity has been refused, dismissed, or not accepted by another entity.
-
B.
rejectedBecause
chosen
Indicates that one entity refused, dismissed, or did not accept another entity specifically due to a stated reason or cause.
-
C.
nameProposedBy
Indicates that one entity is the proposer or originator of a particular name assigned to another entity.
-
D.
rejectedIn
Indicates that an entity or proposal was not accepted or was turned down within a specific context, process, or location.
-
E.
rejectedPractice
Indicates that one party has refused to accept, endorse, or continue a particular practice, method, or behavior associated with another party.
- 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_69bd4419393c819086319a6fe4bf8542 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd72e49b048190bac55d9e7a6f7963 |
completed | March 20, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_69bd71447fe88190bb62c5e8753da7a7 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:32 p.m.