Triple
T26721503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UWF Field House |
E673713
|
entity |
| Predicate | primaryUseFor |
P125948
|
FINISHED |
| Object | UWF Argonauts basketball games |
—
|
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: UWF Argonauts basketball games | Statement: [UWF Field House, primaryUseFor, UWF Argonauts basketball games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryUseFor Context triple: [UWF Field House, primaryUseFor, UWF Argonauts basketball games]
-
A.
primaryUseOf
Indicates that one entity serves as the main or principal function, purpose, or application of another entity.
-
B.
primaryUseStart
Indicates the point in time or event at which the primary use or main function of something begins.
-
C.
isPrimarilyUsedAs
chosen
Indicates that one entity serves mainly or most commonly in the role, function, or purpose specified by the other entity.
-
D.
primaryUseArea
Indicates the main functional area or domain in which an entity is primarily used or applied.
-
E.
primaryHumanUse
Indicates the main way humans typically use, interact with, or benefit from the referenced entity.
- 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_69eecda481d08190aea69f2f7c745f56 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69fe96c2647c819082989f11e1ae3d35 |
completed | May 9, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69fe928615448190af939e5a94be55bb |
completed | May 9, 2026, 1:48 a.m. |
Created at: April 27, 2026, 3:40 a.m.