Triple
T32559010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Sims 2 (music contribution) |
E832169
|
entity |
| Predicate | aliasOfContributor |
P82998
|
FINISHED |
| Object | Junkie XL is Tom Holkenborg |
—
|
NE NERFINISHED |
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: Junkie XL is Tom Holkenborg | Statement: [The Sims 2 (music contribution), aliasOfContributor, Junkie XL is Tom Holkenborg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aliasOfContributor Context triple: [The Sims 2 (music contribution), aliasOfContributor, Junkie XL is Tom Holkenborg]
-
A.
creatorAlias
chosen
Indicates that an alternative or secondary name is used to refer to the creator of an entity.
-
B.
associatedName
Indicates that one entity has an alternative or related name that is linked or connected to another entity.
-
C.
subjectAlias
Indicates that one entity is an alternative name, label, or alias referring to the same subject as another entity.
-
D.
hasAuthorAlias
Indicates that an entity (such as a person or author record) is known by an alternative name or pseudonym used as an author.
-
E.
knownAsBy
Indicates that one entity is referred to or recognized by another entity using a particular name or designation.
- 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_69f34926b9848190ace47d2dd0a0de7c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c604600481908a261d74bdf50bee |
completed | May 3, 2026, 3:50 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:03 a.m.