Triple
T36479553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Detroit City FC |
E898770
|
entity |
| Predicate | ticketDemandCharacteristic |
P27056
|
FINISHED |
| Object | strong home attendance |
—
|
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: strong home attendance | Statement: [Detroit City FC, ticketDemandCharacteristic, strong home attendance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketDemandCharacteristic Context triple: [Detroit City FC, ticketDemandCharacteristic, strong home attendance]
-
A.
ticketDemand
chosen
Indicates that there is a level of desire or need among potential buyers for tickets to an event, service, or offering.
-
B.
ticketingUsage
Indicates how a ticketing system or ticket-based access is used or applied in a given context.
-
C.
ticketingContext
Indicates the situational or operational context in which a ticket (such as a support, event, or issue ticket) is created, managed, or applied.
-
D.
visitorDemand
Indicates a relationship where the level or nature of demand expressed by visitors for something (e.g., a service, location, or resource) is specified or quantified.
-
E.
ticketReservation
Indicates the act of securing one or more tickets in advance for a specific event, service, or journey.
- 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_69f76e5a0e088190a2b6706aeb41723c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.