Triple
T6720309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lega Serie A |
E153375
|
entity |
| Predicate | governsClubCategory |
P4027
|
FINISHED |
| Object | professional football 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 football clubs | Statement: [Lega Serie A, governsClubCategory, professional football clubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsClubCategory Context triple: [Lega Serie A, governsClubCategory, professional football clubs]
-
A.
ownerClub
Indicates that a particular club is the owning or parent organization of a given entity (such as a team, facility, or asset).
-
B.
memberCategory
chosen
Indicates that an entity belongs to or is classified under a specific category or group.
-
C.
supportsClubIdentity
Indicates that one entity actively upholds, reinforces, or contributes to maintaining the identity, values, or character of a club.
-
D.
clubState
Indicates that a club is associated with, based in, or officially belongs to a particular state or regional jurisdiction.
-
E.
registrationCategory
Indicates the classification or type under which an entity is formally registered within a system or registry.
- 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_69c6880afb988190ad88011b48ecfcba |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d137084881908e04ee6b2bd45585 |
completed | March 27, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69c6d08c5d348190a29dee668c398e70 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:07 p.m.