Triple
T5865295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zoomerang leg |
E130377
|
entity |
| Predicate | hasAudienceScale |
P37957
|
FINISHED |
| Object | arena and stadium venues |
—
|
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: arena and stadium venues | Statement: [Zoomerang leg, hasAudienceScale, arena and stadium venues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAudienceScale Context triple: [Zoomerang leg, hasAudienceScale, arena and stadium venues]
-
A.
hasAudienceSize
Indicates the relationship between an entity and the number of people or size of group that receives, views, or engages with it.
-
B.
audienceScale
chosen
Indicates the relative size or reach of the audience associated with an entity, event, or communication.
-
C.
hasAudience
Indicates that an entity is intended to be received, viewed, or engaged with by a particular group of people.
-
D.
supportsAudienceSize
Indicates that one entity is capable of accommodating or handling an audience of a specified size.
-
E.
hasAudienceReception
Indicates the relationship between a work or event and how it is received, perceived, or evaluated by its audience.
- 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_69c0085047dc8190af24e311edad3c07 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ffaef081909faaa7f420a3b9b7 |
completed | March 22, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69c03347e51c81909053bcf34e3b88ab |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:56 p.m.