Triple
T12697023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCAA Division II women's lacrosse |
E303359
|
entity |
| Predicate | hasConferenceTournaments |
P19203
|
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: [NCAA Division II women's lacrosse, hasConferenceTournaments, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConferenceTournaments Context triple: [NCAA Division II women's lacrosse, hasConferenceTournaments, true]
-
A.
hasTournament
Indicates that an entity organizes, hosts, or is associated with a specific tournament.
-
B.
includesConferenceTournaments
chosen
Indicates that the subject entity encompasses or accounts for conference tournaments as part of its scope, structure, or content.
-
C.
hasConferenceSport
Indicates that an institution participates in or is associated with a particular sport within a specific athletic conference.
-
D.
hasBasketballTournament
Indicates that a basketball tournament is organized, hosted, or associated with a particular entity or context.
-
E.
hasPlayoffMeetings
Indicates that the entities have faced each other in playoff competitions or postseason matchups.
- 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_69d7bdef90d48190b46b88270e780946 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d962a32c6481908ddaddae4ea267bf |
completed | April 10, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69d960be63f081908a5ef5ef17a311bf |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:22 p.m.