Triple
T4246841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1996 U.S. Open Cup |
E95549
|
entity |
| Predicate | includesTeamsFromLevel |
P24679
|
FINISHED |
| Object | professional |
—
|
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: professional | Statement: [1996 U.S. Open Cup, includesTeamsFromLevel, professional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesTeamsFromLevel Context triple: [1996 U.S. Open Cup, includesTeamsFromLevel, professional]
-
A.
includesTeam
Indicates that a group, project, or organization has a specific team as one of its constituent members or components.
-
B.
supportsTeamLevel
Indicates that one entity provides assistance, resources, or endorsement to a team as a whole rather than to individual members.
-
C.
alsoIncludesTeamsFrom
chosen
Indicates that something not only includes its primary elements but additionally encompasses teams originating from another specified group, category, or source.
-
D.
includesInvitedTeams
Indicates that certain teams are explicitly included as invited participants in an event, activity, or context.
-
E.
teamLevel
Indicates the hierarchical rank or tier at which a team operates within an organization, competition, or structure.
- 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_69b3453d91548190b4d4ef8fe52aa2ac |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e9b64ac81908dc44eaae6829b50 |
completed | March 12, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69b347f587148190a1830503459939b6 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:05 p.m.