Triple
T35826028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sans Famille |
E1035643
|
entity |
| Predicate | notableAdaptationLanguage |
P206069
|
FINISHED |
| Object | Japanese |
—
|
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: Japanese | Statement: [Sans Famille, notableAdaptationLanguage, Japanese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAdaptationLanguage Context triple: [Sans Famille, notableAdaptationLanguage, Japanese]
-
A.
notableAdaptation
Indicates that one work is a significant adaptation or reinterpretation of another work.
-
B.
notableAdaptationElement
Indicates that one work is a significant adaptation or reinterpretation of another work.
-
C.
notableAdaptationType
Indicates that one work is a significant adaptation of another work in a specific way or medium (e.g., film adaptation, stage adaptation).
-
D.
notableAdaptationStudio
Indicates that a particular studio is especially recognized for creating an adaptation of the subject work or property.
-
E.
notableForAdaptationsOf
Indicates that one entity is recognized or distinguished for creating, producing, or being associated with adaptations of another entity.
- 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_69f76e185ffc8190880b3cdf51decd38 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037ce53de881908cf14141cf3bc570 |
completed | May 12, 2026, 7:17 p.m. |
Created at: May 3, 2026, 4:06 p.m.