Triple
T4392741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivy League women’s volleyball |
E99402
|
entity |
| Predicate | netSport |
P24884
|
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: [Ivy League women’s volleyball, netSport, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: netSport Context triple: [Ivy League women’s volleyball, netSport, true]
-
A.
popularSport
Indicates that a sport is widely liked, followed, or played by many people within a certain group or region.
-
B.
sportsProgram
Indicates a relationship where an entity is a sports-related program, event, or broadcast organized or provided by another entity.
-
C.
sportFocus
Indicates that one entity has a primary emphasis, specialization, or concentration on a particular sport represented by the other entity.
-
D.
sponsorSport
Indicates that one entity financially or materially supports a sport or sporting activity, typically in exchange for promotion or association.
-
E.
sportsAndRecreation
chosen
Indicates a relationship where an entity is associated with, involved in, or designated for sports or recreational activities.
- 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_69b345506b408190b0e3dee616738a7d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35285592881909fcdea225a655950 |
completed | March 12, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69b34f572efc8190bad1e5078cbcb75a |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:19 p.m.