Triple
T13300507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aboomoslem Mashhad F.C. |
E316797
|
entity |
| Predicate | hasHomeFansNickname |
P109410
|
FINISHED |
| Object | Aboomoslem supporters |
—
|
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: Aboomoslem supporters | Statement: [Aboomoslem Mashhad F.C., hasHomeFansNickname, Aboomoslem supporters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeFansNickname Context triple: [Aboomoslem Mashhad F.C., hasHomeFansNickname, Aboomoslem supporters]
-
A.
hasFanAbbreviation
Indicates that an entity is associated with an abbreviation or short form commonly used by fans to refer to it.
-
B.
homeArenaNickname
Indicates the commonly used or informal nickname of a team's or organization's home arena.
-
C.
notableTeamNickname
Indicates that a team is commonly known by a particular nickname that is notable or widely recognized.
-
D.
teamNickname
Indicates the commonly used informal or symbolic name by which a team is known.
-
E.
mainStadiumNickname
Indicates the commonly used nickname by which a main stadium is known.
- F. None of above. chosen
Provenance (4 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_69d806b40ab4819094adf6c374f4811a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6893708190aeebf4c47386cff7 |
completed | April 11, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69d99cf7f9c48190a6a4f452b4a2aefa |
completed | April 11, 2026, 12:59 a.m. |
Created at: April 9, 2026, 9:28 p.m.