Triple
T7827358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scudetto shield |
E181279
|
entity |
| Predicate | nonTransferableBetweenClubs |
P18801
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Scudetto shield, nonTransferableBetweenClubs, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonTransferableBetweenClubs Context triple: [Scudetto shield, nonTransferableBetweenClubs, true]
-
A.
nonTransferable
chosen
Indicates that a right, asset, or privilege cannot be legally or contractually transferred from one party to another.
-
B.
canLoanPlayersTo
Indicates that one entity has the authority or ability to temporarily transfer its players to another entity.
-
C.
movedToClub
Indicates that an entity has transferred or changed affiliation from one club to another club.
-
D.
excludedFromFranchise
Indicates that an entity is not allowed to participate in or benefit from a particular franchise or franchising arrangement.
-
E.
transferLine
Indicates a relationship where something is moved or conveyed from one point, medium, or entity to another along a defined path or channel.
- 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_69ca8282ccec819083c48efb72d21cf9 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb04a7f3b8819080f8a8283d6118fb |
completed | March 30, 2026, 11:18 p.m. |
| PD | Predicate disambiguation | batch_69cae91ae008819098e56bbe51143b31 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:43 p.m.