Triple
T32986291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duhok Stadium |
E843955
|
entity |
| Predicate | usedByRegionalTeam |
P189356
|
FINISHED |
| Object | Kurdistan national football team (occasionally) |
—
|
NE NERFINISHED |
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: Kurdistan national football team (occasionally) | Statement: [Duhok Stadium, usedByRegionalTeam, Kurdistan national football team (occasionally)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByRegionalTeam Context triple: [Duhok Stadium, usedByRegionalTeam, Kurdistan national football team (occasionally)]
-
A.
usedByTeam
Indicates that something (such as a resource, tool, or method) is utilized or employed by a particular team.
-
B.
usedForTeamInState
Indicates that something serves as a team or is utilized by a team within a specified state or jurisdiction.
-
C.
usedForTeam
Indicates that something is utilized or designated for use by a particular team.
-
D.
usedByTeams
chosen
Indicates that something (such as a tool, resource, or process) is utilized or employed by one or more teams.
-
E.
usedByDivision
Indicates that something (such as a resource, tool, or asset) is utilized or employed by a particular division within an organization.
- 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_69f3494c6f9c8190a255409fce8b1d3b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 1, 2026, 1:22 a.m.