Triple
T1668619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premier League Manager of the Month |
E36071
|
entity |
| Predicate | expertPanelWeight |
P6679
|
FINISHED |
| Object | 90% |
—
|
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: 90% | Statement: [Premier League Manager of the Month, expertPanelWeight, 90%]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expertPanelWeight Context triple: [Premier League Manager of the Month, expertPanelWeight, 90%]
-
A.
sectorWeighting
Indicates the proportion or emphasis assigned to a particular sector within a broader portfolio, index, or classification.
-
B.
advisorGroup
Indicates a relationship where an advisor is associated with or belongs to a particular advisory group or committee.
-
C.
evaluationBasis
Indicates the criteria, standards, or reference framework used to judge, assess, or measure something in an evaluation process.
-
D.
rankingImpact
Indicates how an entity’s position or level in a ranking is affected or influenced by another factor or action.
-
E.
weightingMethod
chosen
Indicates how relative importance or influence is assigned to elements within a set, such as criteria, features, or data points, in a calculation or decision process.
- 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_69a8861286808190939afff3ce8ee31e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abc0e8d5648190915ff689c7ca42bc |
completed | March 7, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_69a907d331748190963d4ab1a2741537 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:29 p.m.