Triple
T794564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish Cup |
E16989
|
entity |
| Predicate | participationLevel |
P3669
|
FINISHED |
| Object | professional clubs |
—
|
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: professional clubs | Statement: [Scottish Cup, participationLevel, professional clubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: participationLevel Context triple: [Scottish Cup, participationLevel, professional clubs]
-
A.
participation
Indicates that an entity takes part in, contributes to, or is involved in a shared activity, event, or process with others.
-
B.
engagementLevel
chosen
Indicates the degree or intensity of involvement, interest, or participation one entity has in relation to another entity, activity, or context.
-
C.
participationModel
Indicates how entities are involved in or contribute to an activity, process, or interaction.
-
D.
regulatesParticipationIn
Indicates that one entity controls, directs, or sets rules governing another entity’s involvement in an activity, process, or system.
-
E.
participantType
Indicates the specific role or category that a participant has within a given event, activity, or relationship.
- 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_69a4936cb7448190914f5fe4b8d81607 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a79b976c819085cd381bbd597ca5 |
completed | March 1, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69a4a510f61881909175d6d8719246cd |
completed | March 1, 2026, 8:44 p.m. |
Created at: March 1, 2026, 7:38 p.m.