Triple
T15237820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert Morris College |
E364172
|
entity |
| Predicate | hadEsportsProgram |
P117684
|
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: [Robert Morris College, hadEsportsProgram, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadEsportsProgram Context triple: [Robert Morris College, hadEsportsProgram, yes]
-
A.
isEsportsDivisionOf
Indicates that one organization functions as the esports division or competitive gaming branch of another, typically larger, parent organization.
-
B.
isOfficialEsportsTeamOf
Indicates that a team is formally recognized or designated as the official esports representative of a particular organization, brand, or entity.
-
C.
hasEsportsTitle
Indicates that an entity possesses or has been awarded a specific esports-related title or championship.
-
D.
ownsEsportsFranchise
Indicates that one entity has ownership or controlling stake in an esports franchise associated with another entity.
-
E.
hasEsport
Indicates that an entity is associated with or participates in a specific electronic sports (esports) activity or competition.
- 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007da7e988190925a9b67b8070bc7 |
completed | April 15, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69deca899d5c8190be4a7c71e1683c69 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2ca6148190967c319728ec3661 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:12 a.m.