Triple
T22363400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Watanabe |
E552835
|
entity |
| Predicate | isSurnamedBy |
P110914
|
FINISHED |
| Object | actors |
—
|
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: actors | Statement: [Watanabe, isSurnamedBy, actors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSurnamedBy Context triple: [Watanabe, isSurnamedBy, actors]
-
A.
isSurname
chosen
Indicates that one entity is the family name (last name) of another entity.
-
B.
isCountableAsSurname
Indicates that something can be considered or treated as a valid surname for counting or classification purposes.
-
C.
isMatronymicOf
Indicates that one entity is a name or designation derived from the mother of another entity, typically used as that entity’s family or identifying name.
-
D.
hasBaseSurname
Indicates that an entity’s surname is derived from, or fundamentally corresponds to, a specified base or canonical surname.
-
E.
hasSurnamePrefix
Indicates that one entity’s surname begins with, or is prefixed by, the string or component specified by the other entity.
- 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_69e11e4affcc8190ba7c27d29062558d |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f157d616748190921bd49039b7f6fc |
completed | April 29, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69e73011e6388190a05edf137f488441 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:44 p.m.