Triple
T30316584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rue Oberkampf |
E771070
|
entity |
| Predicate | hasNightlifeDistrictStatus |
P101053
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Rue Oberkampf, hasNightlifeDistrictStatus, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNightlifeDistrictStatus Context triple: [Rue Oberkampf, hasNightlifeDistrictStatus, true]
-
A.
hasNightlifeArea
Indicates that a place contains or is associated with an area characterized by nightlife activities such as bars, clubs, or evening entertainment venues.
-
B.
nightlifeDensity
Indicates how concentrated or abundant nightlife-related venues and activities are within a given area.
-
C.
isEntertainmentDistrict
chosen
Indicates that a location functions primarily as an area dedicated to entertainment activities, venues, and nightlife.
-
D.
hasStreetLifeCharacteristic
Indicates that an entity exhibits a particular quality, feature, or condition related to street life or street-level activity.
-
E.
hasDowntownCharacteristic
Indicates that something possesses a feature, quality, or attribute typically associated with a downtown area.
- 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_69f22488f224819081b0f3ec41ab975c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68193b2b08190a00f08dbba490563 |
completed | May 2, 2026, 10:58 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:51 p.m.