Triple
T14177129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A&M Recording Studios, Los Angeles |
E351361
|
entity |
| Predicate | originalSiteBuilt |
P113114
|
FINISHED |
| Object | 1917 |
—
|
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: 1917 | Statement: [A&M Recording Studios, Los Angeles, originalSiteBuilt, 1917]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalSiteBuilt Context triple: [A&M Recording Studios, Los Angeles, originalSiteBuilt, 1917]
-
A.
originalSiteUse
Indicates the historical or initial functional use or purpose assigned to a particular site before any subsequent changes or developments.
-
B.
originalWebsite
Indicates that one entity is the original or primary website from which another entity (such as a copy, mirror, or derivative site) is derived.
-
C.
originallyBuilt
Indicates that one entity was the first or initial builder or constructor of another entity.
-
D.
originSite
Indicates the place or site from which something or someone originally comes or is derived.
-
E.
originalBuilding
Indicates that a building is the initial or first version from which later buildings, modifications, or replacements are derived.
- 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_69d8278834a08190b0f1784e58d7b99c |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61c76e8081909994b95b631100e9 |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05baed64819096590e5618a3a8ed |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239a02e881909b0e2679487e4ab2 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 10, 2026, 1:02 a.m.