Triple
T26069008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mann Cup |
E657487
|
entity |
| Predicate | originalCompetitionType |
P2440
|
FINISHED |
| Object | senior men's field lacrosse |
—
|
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: senior men's field lacrosse | Statement: [Mann Cup, originalCompetitionType, senior men's field lacrosse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalCompetitionType Context triple: [Mann Cup, originalCompetitionType, senior men's field lacrosse]
-
A.
typeOfCompetition
chosen
Indicates the specific kind or category of competition in which an entity participates or is involved.
-
B.
originalCompetitionName
Indicates the name of the competition as it was originally titled or first known, before any later changes or rebranding.
-
C.
associatedCompetitionType
Indicates that one entity is linked to or involved with a particular type or category of competition.
-
D.
overseesCompetitionType
Indicates that one entity has responsibility for supervising, managing, or regulating a particular type or category of competition.
-
E.
officialCompetition
Indicates that there is a formally recognized or sanctioned competition relationship between the entities.
- 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_69ee5bbe539081909efc7f9dd7c1b53c |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: April 26, 2026, 7:27 p.m.