Triple
T32510024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Croft |
E830905
|
entity |
| Predicate | usedAsTitleCharacterSurname |
P195053
|
FINISHED |
| Object | Lara Croft: Tomb Raider |
—
|
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: Lara Croft: Tomb Raider | Statement: [Croft, usedAsTitleCharacterSurname, Lara Croft: Tomb Raider]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsTitleCharacterSurname Context triple: [Croft, usedAsTitleCharacterSurname, Lara Croft: Tomb Raider]
-
A.
usedAsFictionalCharacterSurname
Indicates that a surname is employed as the last name of a fictional character in a narrative work.
-
B.
usedAsSurname
Indicates that something functions as a family name borne by a person or group of people.
-
C.
usedSurnameFor
Indicates that one entity adopted or employed another entity’s surname as the name by which they were known or referred to.
-
D.
usedAsTitleBeforeName
Indicates that a term or phrase functions as a formal title placed immediately before a person's name.
-
E.
hasCharacterWithSurname
Indicates that an entity (such as a work or story) includes at least one character whose surname matches the specified name.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd9ff026a48190bfec33deeb3b2c43 |
completed | May 8, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69fd97d805bc8190ba12f429d3ad04c7 |
completed | May 8, 2026, 7:59 a.m. |
| PDg | Predicate description generation | batch_69fd9fef7aac819089cc88dd3d00296d |
completed | May 8, 2026, 8:33 a.m. |
Created at: May 1, 2026, 1 a.m.