Triple
T24861602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haad Salad |
E622165
|
entity |
| Predicate | isLessKnownFor |
P157418
|
FINISHED |
| Object | nightlife |
—
|
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: nightlife | Statement: [Haad Salad, isLessKnownFor, nightlife]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLessKnownFor Context triple: [Haad Salad, isLessKnownFor, nightlife]
-
A.
isLesserKnown
Indicates that one entity is less widely recognized, famous, or familiar than another comparable entity.
-
B.
isLesserKnownWork
Indicates that one work is relatively less famous, recognized, or widely known compared to other works (typically by the same creator or within the same domain).
-
C.
isLesserKnownWorkOf
Indicates that one work is a less famous or less widely recognized creation of a particular creator or artist.
-
D.
namedForKnownFor
Indicates that one entity is named after another entity specifically because that other entity is notable or recognized for something.
-
E.
nowKnownFor
Indicates that an entity is currently recognized or notable for a particular role, attribute, achievement, or association.
- F. None of above. chosen
Provenance (4 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_69e2fac350d08190b3affde1b451a8c5 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f4303fad6c8190844f069164f0904d |
completed | May 1, 2026, 4:46 a.m. |
Created at: April 18, 2026, 5:22 a.m.