Triple
T34411461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maria Tura |
E883278
|
entity |
| Predicate | usesPerformanceAsCover |
P188459
|
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: [Maria Tura, usesPerformanceAsCover, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPerformanceAsCover Context triple: [Maria Tura, usesPerformanceAsCover, yes]
-
A.
usedCover
Indicates that one entity employed another entity as a protective or concealing cover in a given context.
-
B.
isForPerformanceIn
Indicates that something (such as an item, space, or arrangement) is intended to be used in or associated with a particular performance event.
-
C.
maintainsCoverAs
chosen
Indicates that one entity continues to uphold or preserve a deceptive or protective disguise, identity, or role in relation to another entity.
-
D.
performanceUse
Indicates that something is used, employed, or utilized in the course of performing an action, task, or function.
-
E.
isCover
Indicates that one entity functions as a protective or concealing layer over 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_69f349c1f2208190a09a489bb8b2719d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 1, 2026, 1:59 a.m.