Triple
T34417577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lija |
E883437
|
entity |
| Predicate | fireworksFestivalReputation |
P178922
|
FINISHED |
| Object | among most renowned in Malta |
—
|
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: among most renowned in Malta | Statement: [Lija, fireworksFestivalReputation, among most renowned in Malta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fireworksFestivalReputation Context triple: [Lija, fireworksFestivalReputation, among most renowned in Malta]
-
A.
carnivalReputation
Indicates the perceived status, esteem, or notoriety associated with a carnival within a community or context.
-
B.
preFireReputation
Indicates the reputation or standing an entity had before a particular fire-related event or incident occurred.
-
C.
fanExperienceReputation
Indicates the perceived quality or reputation of the experience that fans have with a person, organization, or event.
-
D.
fightingReputation
Indicates a recognized standing or notoriety an entity has based on its history or perceived ability in fights or combat.
-
E.
crowdReputation
Indicates the collective opinion or perceived standing of an entity as judged by a group or general audience.
- 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_69f349c2e3b88190a67834eb5bcffeaf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f719cc31ec819099bebcf833b14d76 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69f719458378819081725f544efb1173 |
completed | May 3, 2026, 9:45 a.m. |
Created at: May 1, 2026, 2 a.m.