Triple
T30907935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Holiday in Harlem |
E787355
|
entity |
| Predicate | hasNeighborhoodSetting |
P4813
|
FINISHED |
| Object | Harlem |
—
|
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: Harlem | Statement: [A Holiday in Harlem, hasNeighborhoodSetting, Harlem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNeighborhoodSetting Context triple: [A Holiday in Harlem, hasNeighborhoodSetting, Harlem]
-
A.
hasNeighbourhood
chosen
Indicates that one entity is located within, or is associated with, a particular neighborhood area of another entity.
-
B.
hasNeighbourhoodStatus
Indicates that an entity has a particular status, classification, or condition specifically in relation to a given neighbourhood.
-
C.
hasNeighborhoodBase
Indicates that one topological space has a specified collection of neighborhoods at each point that forms a neighborhood base for its topology.
-
D.
hasNeighbourhoodCount
Indicates the number of neighbourhoods associated with a given entity.
-
E.
hasNeighborhoodRole
Indicates that an entity holds a specific role, function, or position within a neighborhood or local community context.
- 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_69f224be300c8190a6513ce1ee0a7026 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fec4cffed08190b5e5e7cc0c87493e |
completed | May 9, 2026, 5:23 a.m. |
| PD | Predicate disambiguation | batch_69fec2ea7fe08190bd751b39515f69d1 |
completed | May 9, 2026, 5:15 a.m. |
Created at: April 29, 2026, 8:50 p.m.