Triple
T20373328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plaza Sound Studios |
E497627
|
entity |
| Predicate | recordingFacilityType |
P2836
|
FINISHED |
| Object | multi-track studio |
—
|
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: multi-track studio | Statement: [Plaza Sound Studios, recordingFacilityType, multi-track studio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordingFacilityType Context triple: [Plaza Sound Studios, recordingFacilityType, multi-track studio]
-
A.
designedFacilityType
Indicates the type or category of facility that something (such as a plan, system, or component) is specifically designed for.
-
B.
productionFacilityType
Indicates the specific kind or category of facility where production or manufacturing activities take place.
-
C.
hasFacilityType
chosen
Indicates that an entity possesses or is associated with a specific type or category of facility.
-
D.
fccFacilityType
Indicates the specific type or classification of a facility as defined by the FCC (Federal Communications Commission).
-
E.
facility
Indicates that one entity is a building, installation, or physical infrastructure used to host, support, or enable the operations or activities of another entity.
- 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_69e0b4a5b7908190a972e4e7e698ae94 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e678aad7b08190a710a75d6828b21e |
completed | April 20, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69e57648be3c81908256838228cabf5c |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:27 a.m.