Triple
T25832408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Derbi Capitalino |
E650699
|
entity |
| Predicate | clubTypeInvolved |
P159331
|
FINISHED |
| Object | professional football club |
—
|
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 football club | Statement: [Derbi Capitalino, clubTypeInvolved, professional football club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clubTypeInvolved Context triple: [Derbi Capitalino, clubTypeInvolved, professional football club]
-
A.
involvesClub
Indicates that an action, event, or relationship includes or is associated with a specific club as a participating entity.
-
B.
clubScope
Indicates that something is within the organizational, functional, or contextual scope of a particular club.
-
C.
clubFrom
Indicates that one entity is the club or organization from which another entity originates, is affiliated, or is derived.
-
D.
participatingClubsFrom
Indicates that certain clubs are taking part in or are involved in an event, activity, or context originating from a specified source or organizer.
-
E.
memberClubsType
Indicates that an entity is associated as a member with clubs of a specified type or category.
- 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_69e7ab37438081908f1ccf6284839520 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f601f26f0c81908f0ee76b955e9806 |
completed | May 2, 2026, 1:53 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 22, 2026, 7:39 a.m.