Triple
T18986318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mouraria |
E464566
|
entity |
| Predicate | hasMusicVenueType |
P114859
|
FINISHED |
| Object | fado house |
—
|
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: fado house | Statement: [Mouraria, hasMusicVenueType, fado house]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMusicVenueType Context triple: [Mouraria, hasMusicVenueType, fado house]
-
A.
hasEntertainmentVenue
Indicates that an entity possesses, contains, or is associated with an entertainment venue as part of its facilities or offerings.
-
B.
hasMusicCategory
chosen
Indicates that something is associated with, classified under, or belongs to a particular category or type of music.
-
C.
hasMusicFacility
Indicates that an entity provides or includes a dedicated facility or resources for music-related activities.
-
D.
hasLiveMusic
Indicates that a place or event features live musical performances as part of its offerings.
-
E.
hasMusicInstitution
Indicates that an entity is associated with or hosts a music-related institution, such as a conservatory, music school, or similar organization.
- 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_69d8dd008af48190a97ff1c6488edf1b |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d660835c8190bedd78590b3e0a7e |
completed | April 20, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f88e0c81908cb20f08bf24cd32 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:01 p.m.