Triple
T35825988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malot |
E1035642
|
entity |
| Predicate | hasNotableWorkAssociatedViaBearer |
P458
|
FINISHED |
| Object | Sans Famille |
E1035643
|
NE 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: Sans Famille | Statement: [Malot, hasNotableWorkAssociatedViaBearer, Sans Famille]
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 (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_69f76e185ffc8190880b3cdf51decd38 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38a4dd462881909067994b24b9189c |
completed | June 22, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.