Triple
T22006421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turnstile |
E543458
|
entity |
| Predicate | signedToLabelInYear |
P83174
|
FINISHED |
| Object | Roadrunner Records 2017 |
—
|
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: Roadrunner Records 2017 | Statement: [Turnstile, signedToLabelInYear, Roadrunner Records 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signedToLabelInYear Context triple: [Turnstile, signedToLabelInYear, Roadrunner Records 2017]
-
A.
signedOnAnniversaryOf
Indicates that an agreement or document was signed on the anniversary date of a specific prior event or reference point.
-
B.
signedAs
Indicates that an entity has signed or endorsed something using a particular name, role, or identity.
-
C.
signedTo
Indicates that one entity has formally entered into a contract or agreement with another, typically for representation, employment, or services.
-
D.
signedWithTeamYear
chosen
Indicates that an entity (typically a player) signed a contract with a specific team in a particular year.
-
E.
yearSigned
Indicates the specific year in which an agreement, contract, or document was formally signed.
- 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_69e11e2db934819095556760c7d85e4d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127a0afa881908318a4ebe211ca28 |
completed | April 28, 2026, 9:33 p.m. |
| PD | Predicate disambiguation | batch_69e6f62dc9d88190ae387f145f9528de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:21 p.m.