Triple
T4673049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Topeka Tropics |
E103609
|
entity |
| Predicate | usesAmericanRules |
P58779
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Topeka Tropics, usesAmericanRules, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesAmericanRules Context triple: [Topeka Tropics, usesAmericanRules, true]
-
A.
usesNCAARules
Indicates that one entity applies or follows NCAA rules in its activities, operations, or decision-making.
-
B.
playedUnderRulesOf
Indicates that an activity or game was conducted in accordance with a specified set of rules or regulations.
-
C.
timeUnderControlOfUnitedStates
Indicates that, during a specified time period, the referenced entity was under the political or administrative control of the United States.
-
D.
usesHomeCourtFormat
Indicates that a competition or series is organized using a format where one participant gains the advantage of playing on their designated home court or venue.
-
E.
umpires
Indicates that an entity serves as the umpire overseeing, judging, or officiating an event, activity, or interaction involving another entity.
- 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_69bd43dda32c8190938b37744ca270fc |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd655aceb081908100ffc0498fe183 |
completed | March 20, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69bd6215864c8190b50ba0f63ba87d0c |
completed | March 20, 2026, 3:04 p.m. |
| PDg | Predicate description generation | batch_69bd655719dc8190beb6942f343a0ae7 |
completed | March 20, 2026, 3:18 p.m. |
Created at: March 20, 2026, 1:15 p.m.