Triple
T34521480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arctic Service Ribbon |
E886289
|
entity |
| Predicate | isTheaterServiceRibbon |
P179437
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Arctic Service Ribbon, isTheaterServiceRibbon, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTheaterServiceRibbon Context triple: [Arctic Service Ribbon, isTheaterServiceRibbon, yes]
-
A.
serviceTheater
Indicates that a service or activity is performed in, for, or in relation to a theater or theatrical venue.
-
B.
isPartOfTheater
Indicates that one entity functions as a component, section, or subdivision within a larger theater (such as a theater building, complex, or organizational unit).
-
C.
theaterSupport
Indicates that one entity provides assistance, resources, or services to support another entity in the context of theater or theatrical activities.
-
D.
isIndoorTheatre
Indicates that a theatre is located indoors rather than outdoors.
-
E.
appliesToTheater
Indicates that something is relevant or applicable specifically to a theater or theatrical context.
- 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_69f349ccc290819089d8e82698e53cb6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f720cc1bfc8190a16118e3af8e9316 |
completed | May 3, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71fb0172c81908f23e95ff16b0dec |
completed | May 3, 2026, 10:13 a.m. |
Created at: May 1, 2026, 2:02 a.m.