Triple
T37671499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Bossu (1959 film) |
E937968
|
entity |
| Predicate | adaptationOfWorkInLanguage |
P121206
|
FINISHED |
| Object | French |
—
|
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: French | Statement: [Le Bossu (1959 film), adaptationOfWorkInLanguage, French]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adaptationOfWorkInLanguage Context triple: [Le Bossu (1959 film), adaptationOfWorkInLanguage, French]
-
A.
adaptedInLanguage
chosen
Indicates that a work or content has been modified or translated so it can be presented or understood in a specified language.
-
B.
librettoAdaptationToLanguage
Indicates that a libretto has been adapted or translated into a specific target language.
-
C.
adaptedWorkOf
Indicates that one work is derived from, based on, or reinterprets the content of another pre-existing work.
-
D.
adaptedIntoWork
Indicates that an original work has been transformed or re-created into another work, typically in a different medium or format.
-
E.
collaboratedOnAdaptationOf
Indicates that two or more entities worked together on creating or producing an adaptation of an existing work.
- 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_69f76ed7b1408190ba8c93c53cb8becf |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:18 p.m.