Triple
T14177127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A&M Recording Studios, Los Angeles |
E351361
|
entity |
| Predicate | openedAsA&M |
P6141
|
FINISHED |
| Object | 1966 |
—
|
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: 1966 | Statement: [A&M Recording Studios, Los Angeles, openedAsA&M, 1966]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsA&M Context triple: [A&M Recording Studios, Los Angeles, openedAsA&M, 1966]
-
A.
openedAs
chosen
Indicates that one entity began operating, functioning, or being available to the public under the form, name, or role of another entity.
-
B.
openedAsBRT
Indicates that a transit service, corridor, or route was initially launched or began operation specifically as a bus rapid transit (BRT) system.
-
C.
openingTo
Indicates that one entity serves as an entrance, access point, or passage leading into or toward another entity.
-
D.
openingBeganApproxMa
Indicates the approximate time in millions of years ago when an opening or separation process (such as rifting or basin formation) began.
-
E.
openedDuring
Indicates that an entity began operating, became accessible, or was inaugurated within a specified time period or event.
- 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_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. |
Created at: April 10, 2026, 1:02 a.m.