Triple
T7550111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ligue 1 Player of the Month |
E178507
|
entity |
| Predicate | hasFanEngagementAspect |
P18289
|
FINISHED |
| Object | public voting |
—
|
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: public voting | Statement: [Ligue 1 Player of the Month, hasFanEngagementAspect, public voting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFanEngagementAspect Context triple: [Ligue 1 Player of the Month, hasFanEngagementAspect, public voting]
-
A.
hasFanActivity
chosen
Indicates that an entity is associated with actions, behaviors, or engagement carried out by fans in relation to it.
-
B.
hasFanCommunity
Indicates that an entity is associated with a group of fans who actively follow, support, or engage around it.
-
C.
engagementOf
Indicates a relationship where an engagement, commitment, or formal involvement is associated with or attributed to a specific entity.
-
D.
hasFan
Indicates that an entity is the admirer, supporter, or enthusiast of another entity.
-
E.
fanInvolved
Indicates that a fan actively participates in or is directly involved with a particular event, activity, or interaction.
- 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_69c69f2cbe08819088f9eb0c03ef529b |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8b35ba481908e1e5bbf329daa33 |
completed | March 27, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69c6f4daad6c8190af2b8ae88d2c8cb7 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:49 p.m.