Triple
T19295036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Casa da Música |
E482540
|
entity |
| Predicate | housesResidentEnsemble |
P39079
|
FINISHED |
| Object | Orquestra Sinfónica do Porto Casa da Música |
—
|
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: Orquestra Sinfónica do Porto Casa da Música | Statement: [Casa da Música, housesResidentEnsemble, Orquestra Sinfónica do Porto Casa da Música]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: housesResidentEnsemble Context triple: [Casa da Música, housesResidentEnsemble, Orquestra Sinfónica do Porto Casa da Música]
-
A.
residentEnsemble
chosen
Indicates that an ensemble is based at, regularly performs in, or is formally affiliated with a particular place or institution.
-
B.
houseOrFamily
Indicates that two entities are related through a shared house, household, or family membership.
-
C.
housingPattern
Indicates the typical arrangement or distribution of housing units or residential structures within a given area or context.
-
D.
residenceGroup
Indicates that multiple entities share a common place of residence or are grouped together based on living at the same location.
-
E.
house1
Indicates that something is identified or classified as a house or dwelling.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fc8533c08190822a917ffa32812d |
completed | April 20, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0bc7508190a6f9d56bd4c3404f |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:31 p.m.