Triple
T24579061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russia women’s national futsal team |
E608194
|
entity |
| Predicate | isTopLevelTeamOf |
P29737
|
FINISHED |
| Object | Russian women’s futsal |
—
|
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: Russian women’s futsal | Statement: [Russia women’s national futsal team, isTopLevelTeamOf, Russian women’s futsal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTopLevelTeamOf Context triple: [Russia women’s national futsal team, isTopLevelTeamOf, Russian women’s futsal]
-
A.
includesTeam
chosen
Indicates that a group, project, or organization has a specific team as one of its constituent members or components.
-
B.
hasTeamMember
Indicates that an entity includes another entity as a member of its team.
-
C.
hasTeamFor
Indicates that an entity possesses, is associated with, or is responsible for a specific team designated for a particular purpose or context.
-
D.
hasPartInTeamLegacy
Indicates that an entity contributes to or is included as a component of a team's enduring history, heritage, or long-term legacy.
-
E.
supportsTeamLevel
Indicates that one entity provides assistance, resources, or endorsement to a team as a whole rather than to individual members.
- 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_69e2c4cdab6c8190aae6e5d3de55c95e |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a97cd0d4819091bf0841fa8e108a |
completed | April 30, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:29 a.m.