Triple
T6008806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Campo de' Fiori |
E133779
|
entity |
| Predicate | nightlifePeak |
P60798
|
FINISHED |
| Object | evening |
—
|
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: evening | Statement: [Campo de' Fiori, nightlifePeak, evening]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nightlifePeak Context triple: [Campo de' Fiori, nightlifePeak, evening]
-
A.
nightlifePattern
Indicates a recurring way entities engage in or are associated with nightlife activities, such as typical behaviors, schedules, or participation patterns during night hours.
-
B.
nightlifeCharacter
chosen
Indicates a characteristic or quality associated with nightlife, such as the typical atmosphere, energy, or style of nighttime social activities.
-
C.
offersNightlife
Indicates that a place provides opportunities for nighttime entertainment, such as bars, clubs, or evening events.
-
D.
hasNightlifeArea
Indicates that a place contains or is associated with an area characterized by nightlife activities such as bars, clubs, or evening entertainment venues.
-
E.
prominentAtNight
Indicates that an entity becomes especially noticeable, visible, or significant during nighttime conditions.
- 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_69c0087361a48190905c6b55969852b8 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f154ca481909431baf4feecc16d |
completed | March 22, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69c049e4daf4819099bf870dc700e0a2 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:06 p.m.