Triple
T18148973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sussudio |
E434456
|
entity |
| Predicate | titleWordType |
P130638
|
FINISHED |
| Object | nonsense word |
—
|
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: nonsense word | Statement: [Sussudio, titleWordType, nonsense word]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleWordType Context triple: [Sussudio, titleWordType, nonsense word]
-
A.
titleType
Indicates the specific category or kind of title associated with an entity (e.g., whether it is a main title, alternative title, working title, etc.).
-
B.
titleVariant
Indicates that one title is an alternative or variant form of another title referring to the same work or entity.
-
C.
titleHolderType
Indicates the specific role or capacity in which an entity holds a title (e.g., owner, trustee, beneficiary).
-
D.
titleCreationType
Indicates the manner or process by which a title was generated, assigned, or established for an entity.
-
E.
titlePattern
Indicates that there is a specific structural or textual pattern that the title of an entity is expected to follow.
- 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_69d8b90aac308190801e2c57d8c5bfe5 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4de372e8081908b52fe33c870716e |
completed | April 19, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69e43317d11c81908d1dc14921566b47 |
completed | April 19, 2026, 1:42 a.m. |
| PDg | Predicate description generation | batch_69e438f5ae2c8190b11dee46534fa5a9 |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:29 a.m.