Triple
T5455743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armide |
E122472
|
entity |
| Predicate | librettoForm |
P37066
|
FINISHED |
| Object | French classical alexandrines |
—
|
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 classical alexandrines | Statement: [Armide, librettoForm, French classical alexandrines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: librettoForm Context triple: [Armide, librettoForm, French classical alexandrines]
-
A.
librettoBy
Indicates that a work’s libretto (the text of an opera or similar vocal work) was written by a particular person.
-
B.
includesLibretto
Indicates that one entity (typically a musical or operatic work or publication) contains or is accompanied by the full text/libretto of another work.
-
C.
writingForm
chosen
Indicates the specific script, notation, or written representation used to express a piece of language or content.
-
D.
dramaticForm
Indicates that one entity is expressed, structured, or realized in the form of a particular dramatic genre or theatrical mode.
-
E.
writtenForm
Indicates that one entity is the textual or orthographic representation (spelling or written version) of another entity.
- 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_69bd46424248819085282ddf50a565f3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd927c946c8190aef40679199fede3 |
completed | March 20, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69bd91a0d96c8190bd1299edbf764bbb |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:08 p.m.