Triple
T661610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2020 Summer Olympics |
E11766
|
entity |
| Predicate | spectatorPolicy |
P10265
|
FINISHED |
| Object | mostly without spectators |
—
|
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: mostly without spectators | Statement: [2020 Summer Olympics, spectatorPolicy, mostly without spectators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spectatorPolicy Context triple: [2020 Summer Olympics, spectatorPolicy, mostly without spectators]
-
A.
hasSpectatorArea
Indicates that a location or facility includes a designated area intended for spectators to observe an event or activity.
-
B.
seatSelectionPolicy
Indicates the rules or constraints governing how seats are chosen or assigned in a given context.
-
C.
reservationPolicy
Indicates the rules or conditions governing how reservations are made, modified, or canceled between parties.
-
D.
locationPolicy
Indicates a rule or constraint governing where an entity is allowed, required, or restricted to be located.
-
E.
hasVisitorPolicy
chosen
Indicates that an entity has an established policy governing the presence, behavior, or permissions of visitors.
- 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_69a4932862a0819098be659c814e4981 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49fa954988190841740a587ace466 |
completed | March 1, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69a49d153a948190b3ccdc331ed33617 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.