Triple
T23084226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cotton Club |
E575559
|
entity |
| Predicate | hadAddress |
P4379
|
FINISHED |
| Object | 142nd Street and Lenox Avenue (original Harlem location) |
—
|
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: 142nd Street and Lenox Avenue (original Harlem location) | Statement: [Cotton Club, hadAddress, 142nd Street and Lenox Avenue (original Harlem location)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadAddress Context triple: [Cotton Club, hadAddress, 142nd Street and Lenox Avenue (original Harlem location)]
-
A.
hasAddress
chosen
Indicates that an entity is associated with a specific address or location.
-
B.
address
Indicates that one entity directs spoken or written communication specifically to another entity.
-
C.
addressedThrough
Indicates that an issue, request, or communication is handled, resolved, or processed by means of a specified channel, method, or intermediary.
-
D.
hasFormerAddress
Indicates that an entity was previously located at or associated with a particular address, but no longer is.
-
E.
locationAddressed
Indicates that a communication, message, or action is specifically directed to or intended for a particular location or address.
- 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_69e245bf3e3c819086d3448720efc01b |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18da3d4208190b7bfd1026e773dbf |
completed | April 29, 2026, 4:48 a.m. |
| PD | Predicate disambiguation | batch_69ef89e5ce748190b2c3ac3843484127 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:57 p.m.