Triple
T5812153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Open Cup 2014 |
E128893
|
entity |
| Predicate | includesAmateurTeams |
P12105
|
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: [U.S. Open Cup 2014, includesAmateurTeams, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesAmateurTeams Context triple: [U.S. Open Cup 2014, includesAmateurTeams, true]
-
A.
includesAmateurClubs
chosen
Indicates that something (such as an organization, competition, or structure) contains or encompasses amateur-level clubs as part of it.
-
B.
isAmateur
Indicates that an entity engages in an activity or field on a non-professional, typically unpaid or hobbyist basis.
-
C.
teamEligibility
Indicates whether an entity meets the required conditions to participate as a member of a particular team.
-
D.
hasProfessionalPlayers
Indicates that an entity is associated with or includes individuals who participate in a profession at a professional level.
-
E.
allowsForeignPlayers
Indicates that an entity permits participation or involvement by players who are from foreign countries or outside its primary jurisdiction.
- 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_69c0084788848190bcf71f6bc5d71597 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b54c2848190bb85212689d0b511 |
completed | March 22, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69c021d5ecd081908a62dd66e26f8598 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:52 p.m.