Triple
T22103594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ursule |
E546229
|
entity |
| Predicate | usedAsCoverName |
P21109
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Ursule, usedAsCoverName, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsCoverName Context triple: [Ursule, usedAsCoverName, Yes]
-
A.
usedCover
Indicates that one entity employed another entity as a protective or concealing cover in a given context.
-
B.
hasCoverName
chosen
Indicates that one entity uses or is known by an alternative, often secret or assumed, name in relation to another entity or context.
-
C.
nameUsedIn
Indicates that a particular name is employed or referenced within a specified context, work, or usage setting.
-
D.
nameUsedFor
Indicates that a particular name is used to refer to or designate a given entity.
-
E.
usedAsTitleOnReleasesBy
Indicates that a work or phrase is used as the title on releases (such as albums, singles, or other published items) created by a specific artist or 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_69e11e378dc08190896d6a51597afd5a |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129175a7881909549883f23c53dca |
completed | April 28, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69e71b20ec50819096ac196c798f8e3c |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:30 p.m.