Triple
T37629639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mqabba |
E936304
|
entity |
| Predicate | hasFireworksClub |
P157976
|
FINISHED |
| Object | St Mary Fireworks Factory, Mqabba |
—
|
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: St Mary Fireworks Factory, Mqabba | Statement: [Mqabba, hasFireworksClub, St Mary Fireworks Factory, Mqabba]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFireworksClub Context triple: [Mqabba, hasFireworksClub, St Mary Fireworks Factory, Mqabba]
-
A.
fireworksLocation
Indicates the place where fireworks are set off, displayed, or occur.
-
B.
fireworksCompany
chosen
Indicates a relationship where an entity is a company that produces, sells, or organizes fireworks displays for another entity or context.
-
C.
hasPyrotechnics
Indicates that an entity includes, uses, or features pyrotechnic effects or fireworks as part of its characteristics or activities.
-
D.
hasClubBurgee
Indicates that a club possesses or is associated with a specific burgee (a distinctive club flag or pennant).
-
E.
hasFirecrackerBan
Indicates that a governing body or authority has enacted a prohibition on the use, sale, or possession of firecrackers.
- 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_69f76ed24820819081bafd36e9088701 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00694f72888190983fee7d687a6daa |
completed | May 10, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_6a00685dbf44819098ea0c86bb9e50d8 |
completed | May 10, 2026, 11:13 a.m. |
Created at: May 3, 2026, 4:18 p.m.