Triple
T35825988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malot |
E1035642
|
entity |
| Predicate | hasNotableWorkAssociatedViaBearer |
—
|
GENERATED |
| Object | Sans Famille |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableWorkAssociatedViaBearer Context triple: [Malot, hasNotableWorkAssociatedViaBearer, Sans Famille]
-
A.
hasNotableWorkRights
Indicates that an entity holds legal or recognized rights associated with a notable work, such as authorship, ownership, or usage rights.
-
B.
hasNotableBearer
chosen
Indicates that an entity (such as a name, title, or identifier) is borne by at least one notable person or entity.
-
C.
hasNotableWorkSetThere
Indicates that a notable work (such as a book, film, or other creative piece) is set in or takes place within the referenced location.
-
D.
hasNotableBearerOccupation
Indicates that an entity is associated with a notable person who holds a specific occupation.
-
E.
hasCatalogedWorkOn
Indicates that an entity has formally recorded, listed, or documented another entity as a work within a catalog or collection.
- F. None of above.
Provenance (1 batch)
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_69f76e185ffc8190880b3cdf51decd38 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.