Triple
T9466278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Studio 8G |
E228277
|
entity |
| Predicate | hasAudienceEntrance |
P6140
|
FINISHED |
| Object | Rockefeller Center entrances |
—
|
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: Rockefeller Center entrances | Statement: [Studio 8G, hasAudienceEntrance, Rockefeller Center entrances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAudienceEntrance Context triple: [Studio 8G, hasAudienceEntrance, Rockefeller Center entrances]
-
A.
hasEntrance
chosen
Indicates that one entity possesses or provides an entry point or access way to another entity or space.
-
B.
audienceAccess
Indicates that one entity has permission or ability to access, view, or engage with a particular audience associated with another entity.
-
C.
hasAudienceReception
Indicates the relationship between a work or event and how it is received, perceived, or evaluated by its audience.
-
D.
hasAutomaticEntrance
Indicates that an entity is equipped with an entrance that operates automatically (e.g., opens or closes without manual effort).
-
E.
hasAudience
Indicates that an entity is intended to be received, viewed, or engaged with by a particular group of people.
- 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_69ca846fee388190a6ec273fd644b88b |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7fdc08f08190ad17de08d2c2eca2 |
completed | April 1, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69cca55caaa8819089c5138e014892d3 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:53 p.m.