Triple
T26429511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belardo |
E664462
|
entity |
| Predicate | usedAsCharacterSurnameIn |
P152693
|
FINISHED |
| Object | television series |
—
|
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: television series | Statement: [Belardo, usedAsCharacterSurnameIn, television series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsCharacterSurnameIn Context triple: [Belardo, usedAsCharacterSurnameIn, television series]
-
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.
usedAsSurnameInCountry
Indicates that a particular name functions as a family surname within the specified country.
-
D.
hasCharacterWithSurname
chosen
Indicates that an entity (such as a work or story) includes at least one character whose surname matches the specified name.
-
E.
surnameUsedIn
Indicates that a particular surname is used or borne within a specified context, such as by a person, family, or group.
- 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_69ee883ad6a4819088f918e76122d690 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 26, 2026, 11:48 p.m.