Triple
T31194594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Studio Two |
E795283
|
entity |
| Predicate | primaryRecordingRoomFor |
P5757
|
FINISHED |
| Object | The Beatles |
E18058
|
NE 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: The Beatles | Statement: [Studio Two, primaryRecordingRoomFor, The Beatles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRecordingRoomFor Context triple: [Studio Two, primaryRecordingRoomFor, The Beatles]
-
A.
primaryRecordingSite
Indicates the main anatomical or spatial location where a recording or measurement was originally captured.
-
B.
recordingFor
Indicates that one entity serves as a recorded representation (such as audio, video, or data capture) created for, or documenting, another entity or event.
-
C.
primaryReservationLocation
Indicates the main or default location associated with a reservation where it is primarily held or fulfilled.
-
D.
mainChamber
chosen
Indicates that something is the primary or central chamber or room within a larger structure or system.
-
E.
primaryTheater
Indicates that a particular location or region is the main setting or principal area where an event, activity, or operation takes place.
- F. None of above.
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_69f224d7a6a481908187c4362a8a525f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2958fe49c0819091d3489fef45e870 |
completed | June 10, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:09 p.m.