Triple
T35625688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GLOW wrestling promotion |
E1029444
|
entity |
| Predicate | hasAudienceWithinFiction |
P138908
|
FINISHED |
| Object | live studio crowd |
—
|
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: live studio crowd | Statement: [GLOW wrestling promotion, hasAudienceWithinFiction, live studio crowd]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAudienceWithinFiction Context triple: [GLOW wrestling promotion, hasAudienceWithinFiction, live studio crowd]
-
A.
eraWithinFiction
Indicates that a time period or era exists inside the narrative world or timeline of a fictional work.
-
B.
targetAudienceWithinFiction
chosen
Indicates that the intended audience of a work exists as characters or entities within the fictional world depicted by that work.
-
C.
hasViewOfFictional
Indicates that one entity has a visual or conceptual perspective of a fictional entity or scene.
-
D.
audienceCompositionInFiction
Indicates the relationship between a fictional work and the makeup or characteristics of the audience depicted within that fictional context.
-
E.
hasEventInFiction
Indicates that a fictional work includes or depicts a particular event within its narrative.
- 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_69f76e07bb0c8190968ea2d836fc42c9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
Created at: May 3, 2026, 4:05 p.m.