Triple
T24995328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sōeki |
E625551
|
entity |
| Predicate | bearerAlternativeNameOf |
P93997
|
FINISHED |
| Object | Sen no Rikyū |
—
|
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: Sen no Rikyū | Statement: [Sōeki, bearerAlternativeNameOf, Sen no Rikyū]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bearerAlternativeNameOf Context triple: [Sōeki, bearerAlternativeNameOf, Sen no Rikyū]
-
A.
bearerAnglicizedNameOf
Indicates that one entity is the anglicized (English-adapted) version of the name borne by another entity.
-
B.
hasAlternativeFamilyName
Indicates that an entity is associated with an additional or variant family name besides its primary family name.
-
C.
bearerShortName
Indicates that an entity serves as the short or abbreviated name used to identify the bearer in the context of a relationship or action.
-
D.
bearerByname
chosen
Indicates that an entity is known or referred to by a particular byname or secondary name.
-
E.
hasAlternativeBearers
Indicates that an entity can be carried, represented, or borne by more than one possible bearer or carrier as alternatives.
- 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_69e2ff2611c081908710457fbe6d376b |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 18, 2026, 6:04 a.m.