Triple
T13662168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Axur, re d'Ormus |
E327023
|
entity |
| Predicate | librettoAdaptationFromLanguage |
P78807
|
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: [Axur, re d'Ormus, librettoAdaptationFromLanguage, French]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: librettoAdaptationFromLanguage Context triple: [Axur, re d'Ormus, librettoAdaptationFromLanguage, French]
-
A.
originalLanguageOfLibretto
chosen
Indicates the language in which a libretto was originally written for a given work.
-
B.
librettoBy
Indicates that a work’s libretto (the text of an opera or similar vocal work) was written by a particular person.
-
C.
broadwayAdaptationLanguage
Indicates the language in which a Broadway adaptation of a work is performed or produced.
-
D.
librettoStyle
Indicates the stylistic characteristics or manner in which a libretto (the text of an opera or similar work) is written or composed.
-
E.
screenWriterAdaptationBy
Indicates that a person served as the screenwriter responsible for adapting an existing work into a screenplay.
- 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_69d8076d8270819092afc2f0e9c359a8 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc620df208190afaccf3ddd10aa60 |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8a027081908d8f884b89707a5e |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:52 p.m.