Triple
T20301561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Syrianska FC |
E505490
|
entity |
| Predicate | fanGroupIdentity |
P75835
|
FINISHED |
| Object | Assyrian/Syriac Christians |
—
|
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: Assyrian/Syriac Christians | Statement: [Syrianska FC, fanGroupIdentity, Assyrian/Syriac Christians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fanGroupIdentity Context triple: [Syrianska FC, fanGroupIdentity, Assyrian/Syriac Christians]
-
A.
fandomIdentity
chosen
Indicates that an entity identifies as a fan or member of a particular fandom associated with another entity.
-
B.
fanOwned
Indicates that the entity is owned or controlled by fans, typically through collective or community-based ownership rather than traditional private or corporate ownership.
-
C.
fanDestination
Indicates that one entity is the intended target or recipient of another entity’s enthusiasm, admiration, or fandom.
-
D.
fanAccess
Indicates that an entity has permission or the ability to access fan-related content, features, or areas associated with another entity.
-
E.
supporterIdentity
Indicates that one entity is identified as a supporter (e.g., backer, advocate, or sponsor) of another entity or cause.
- 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_69e0b4b8ab648190906e18538c250148 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6770d82b48190b21ce7c52ec6d5a0 |
completed | April 20, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:17 a.m.