Triple
T37595608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tex Watson (Once Upon a Time in Hollywood character) |
E935374
|
entity |
| Predicate | hasSurnameInCredits |
P152693
|
FINISHED |
| Object | Watson |
—
|
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: Watson | Statement: [Tex Watson (Once Upon a Time in Hollywood character), hasSurnameInCredits, Watson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurnameInCredits Context triple: [Tex Watson (Once Upon a Time in Hollywood character), hasSurnameInCredits, Watson]
-
A.
hasCharacterWithSurname
chosen
Indicates that an entity (such as a work or story) includes at least one character whose surname matches the specified name.
-
B.
hasComponentSurname
Indicates that an entity’s full name includes a specified surname as one of its component parts.
-
C.
hasNotableSurname
Indicates that an entity bears a surname that is recognized as notable, distinguished, or of particular significance.
-
D.
hasSeptSurname
Indicates that an entity bears a surname associated with a particular sept (a family subgroup or clan division).
-
E.
hasNotablePersonWithSurname
Indicates that an entity is associated with at least one notable person who bears a specified surname.
- 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_69f76ecf39c081909baffe597bb55273 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0059f4ffe481908dc500cee9051148 |
completed | May 10, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_6a00593a3c1881909b2ff1a29eb474b3 |
completed | May 10, 2026, 10:08 a.m. |
Created at: May 3, 2026, 4:18 p.m.