Triple
T34099161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neil Park (Columbus) |
E874515
|
entity |
| Predicate | occasionalUse |
P116266
|
FINISHED |
| Object | Ohio State Buckeyes football games |
—
|
NE NERFINISHED |
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: Ohio State Buckeyes football games | Statement: [Neil Park (Columbus), occasionalUse, Ohio State Buckeyes football games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occasionalUse Context triple: [Neil Park (Columbus), occasionalUse, Ohio State Buckeyes football games]
-
A.
occasionalRange
Indicates that the relationship or action occurs intermittently or at irregular intervals within a specified range or context.
-
B.
oftenUse
Indicates that one entity frequently or regularly uses, employs, or utilizes another entity.
-
C.
usedLessIn
Indicates that one entity is used with a lower frequency or intensity compared to another entity.
-
D.
frequentOccasion
Indicates that a particular event, situation, or condition occurs repeatedly or commonly over time.
-
E.
isSometimesUsedFor
chosen
Indicates that something serves a particular purpose or function on some occasions, but not consistently or exclusively.
- 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_69f349a735208190a1dbfb1c2a121059 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70c6634988190b3fc88269f5611bd |
completed | May 3, 2026, 8:50 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:53 a.m.