Triple
T27746680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AdventHealth Arena |
E702001
|
entity |
| Predicate | hasCompetitionUse |
P199523
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [AdventHealth Arena, hasCompetitionUse, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompetitionUse Context triple: [AdventHealth Arena, hasCompetitionUse, yes]
-
A.
usesCompetition
Indicates that one entity employs or leverages another entity as a competitor or within a competitive context.
-
B.
usedInCompetition
Indicates that something is employed or utilized as part of a competition or contest.
-
C.
hasCompetition
Indicates that one entity is in a state of rivalry or contest with another entity, typically competing for the same goal, resource, or advantage.
-
D.
usesCompetitionSystem
Indicates that an entity operates under or applies a particular competition system or format.
-
E.
hasCompetitionElement
Indicates that one entity includes, involves, or is associated with a specific competitive component, aspect, or feature.
- F. None of above. chosen
Provenance (4 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69ff409ff5548190849c2d50e99bd807 |
completed | May 9, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69ff401a5e188190a72f945e910b4a6c |
completed | May 9, 2026, 2:09 p.m. |
| PDg | Predicate description generation | batch_69ff409ee6ec819088b7c13fabed2ac2 |
completed | May 9, 2026, 2:11 p.m. |
Created at: April 27, 2026, 4:16 p.m.