Triple
T31430618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomb Raider (2018 film score) |
E801785
|
entity |
| Predicate | composerRealName |
P118064
|
FINISHED |
| Object | 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: Tom Holkenborg | Statement: [Tomb Raider (2018 film score), composerRealName, Tom Holkenborg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: composerRealName Context triple: [Tomb Raider (2018 film score), composerRealName, Tom Holkenborg]
-
A.
realNameOfComposer
chosen
Indicates that the object is the actual, full real-world name of the composer referred to by the subject.
-
B.
creatorFullName
Indicates the full personal name of the entity that created or authored another entity.
-
C.
authorRealNameOfCreator
Indicates that a person’s real, legal, or birth name is the true identity behind a creator who may be known by a pseudonym or handle.
-
D.
producerArtist
Indicates that one entity serves as the producer (e.g., overseeing or managing the creation) of a work created or performed by the artist entity.
-
E.
musicalArtistRealName
Indicates that a musical artist is known in real life by a particular personal or legal name.
- 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: April 30, 2026, 8:57 p.m.