Triple
T32854070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georginio Wijnaldum |
E840328
|
entity |
| Predicate | signedForClubFrom |
P175533
|
FINISHED |
| Object | Liverpool FC, Newcastle United |
—
|
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: Liverpool FC, Newcastle United | Statement: [Georginio Wijnaldum, signedForClubFrom, Liverpool FC, Newcastle United]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signedForClubFrom Context triple: [Georginio Wijnaldum, signedForClubFrom, Liverpool FC, Newcastle United]
-
A.
signedFor
Indicates that one entity formally accepted or acknowledged receipt of something on behalf of another, typically by providing a signature.
-
B.
signedFromLeague
Indicates that an entity has been signed or acquired from a specified sports league.
-
C.
signedTo
Indicates that one entity has formally entered into a contract or agreement with another, typically for representation, employment, or services.
-
D.
signedAs
Indicates that an entity has signed or endorsed something using a particular name, role, or identity.
-
E.
signedWithTeam
Indicates that an entity has entered into a formal contract or agreement to join and play for a specific team.
- 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_69f349412c78819084459850e11d29f7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d210fc80819091ed8961aa2cddfb |
completed | May 3, 2026, 4:41 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
| PDg | Predicate description generation | batch_69f6d16b79dc8190ab0d4657f2ef9a5b |
completed | May 3, 2026, 4:39 a.m. |
Created at: May 1, 2026, 1:17 a.m.