Triple
T10799458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RCA Studio B |
E254800
|
entity |
| Predicate | tourIncludes |
P88678
|
FINISHED |
| Object | original recording studio space |
—
|
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: original recording studio space | Statement: [RCA Studio B, tourIncludes, original recording studio space]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tourIncludes Context triple: [RCA Studio B, tourIncludes, original recording studio space]
-
A.
tourWith
Indicates that one entity accompanies another on a tour, sharing the same itinerary or guided experience.
-
B.
tourOf
chosen
Indicates that one entity serves as a guided or organized visit through another entity, typically for exploration, education, or sightseeing.
-
C.
transportIncludes
Indicates that a broader transport operation or service encompasses, contains, or makes use of a specific transport segment, mode, or component as part of its overall movement.
-
D.
tourCategory
Indicates the classification or type of a tour (e.g., by theme, style, or purpose) that the tour belongs to.
-
E.
tourismFeature
Indicates that something serves as an attraction, amenity, or point of interest relevant to tourism or visitors.
- 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_69d6aa61c15c8190a1839550c56e75e1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d733366c408190bfd3b57be5ef2440 |
completed | April 9, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69d6f3188f00819094ee8d65b187a333 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:18 p.m.