Triple
T14905161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NYRR 9+1 program |
E360110
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | participation-based entry system |
C13148
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: participation-based entry system Context triple: [NYRR 9+1 program, instanceOf, participation-based entry system]
-
A.
mass participation event
chosen
A mass participation event is a large-scale organized activity in which a substantial number of people take part simultaneously, typically for a common purpose such as sport, charity, culture, or community engagement.
-
B.
entrance
An entrance is a designated point of access that allows people or objects to move from the outside into a defined space or area.
-
C.
admission ticket
An admission ticket is a physical or digital token that grants an individual the right to enter a specific event, venue, or service at a designated time.
-
D.
limited entry area
A limited entry area is a designated space where access is restricted to authorized individuals or under specific conditions to ensure safety, security, or resource protection.
-
E.
alternate attendance system
An alternate attendance system is a governance mechanism in which regional leaders are required to spend alternating periods of time at a central authority’s court and in their own domains, thereby enabling political control, surveillance, and the balancing of local and central power.
- F. None of above.
Provenance (1 batch)
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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 2:12 a.m.