Triple
T31875872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wq 45 |
E813739
|
entity |
| Predicate | hasTitleOfReferredWork |
P144993
|
FINISHED |
| Object | Armide |
—
|
NE NERFINISHED |
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: Armide | Statement: [Wq 45, hasTitleOfReferredWork, Armide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleOfReferredWork Context triple: [Wq 45, hasTitleOfReferredWork, Armide]
-
A.
hasTitleWork
Indicates that an entity is associated with a specific work by its title (i.e., the entity has or bears that work’s title).
-
B.
hasTitleInOriginalWork
Indicates that an entity holds a specific title or designation within its original work or source context.
-
C.
hasTitleOf
chosen
Indicates that one entity holds, bears, or is designated by the official title, name, or rank specified by another entity.
-
D.
hasCataloguedTitle
Indicates that an entity has a specific title recorded or listed in a catalog or cataloging system.
-
E.
hasWorkingTitle
Indicates that an entity is associated with a provisional or temporary title used during its development or production.
- 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_69f348ed74bc81909846aaa6a3c7318c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: April 30, 2026, 11:55 p.m.