Triple
T14946732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mountain East Conference |
E372680
|
entity |
| Predicate | sponsorsSoftball |
P790
|
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: [Mountain East Conference, sponsorsSoftball, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sponsorsSoftball Context triple: [Mountain East Conference, sponsorsSoftball, true]
-
A.
alsoSponsorsSport
Indicates that an entity that sponsors one sport also sponsors another sport.
-
B.
sponsors
Indicates that one entity provides financial or material support to another, often in exchange for association, promotion, or fulfillment of certain activities or goals.
-
C.
homeSoftballStadiumFor
Indicates that one entity is the designated home softball stadium or primary venue for the softball team or organization represented by the other entity.
-
D.
ballparkNameSponsor
Indicates that a particular sponsor is the naming-rights sponsor for a ballpark.
-
E.
sponsorSport
chosen
Indicates that one entity financially or materially supports a sport or sporting activity, typically in exchange for promotion or association.
- 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_69d85cca979481908747d2a81eba1cea |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded68e35c481908e47cd68441c5115 |
completed | April 15, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69de9a588c2c8190b1245a1c406f447c |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:39 a.m.