Triple
T29722190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M.52 |
E752085
|
entity |
| Predicate | appliesToWorkForm |
P194555
|
FINISHED |
| Object | opera |
—
|
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: opera | Statement: [M.52, appliesToWorkForm, opera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToWorkForm Context triple: [M.52, appliesToWorkForm, opera]
-
A.
appliesToWork
Indicates that something (such as a rule, policy, condition, or attribute) is relevant to, governs, or is in effect for a particular piece of work or work-related activity.
-
B.
appearsInWorkForm
Indicates that something is included or manifested within a particular work or version/form of a work.
-
C.
basedInWorkForm
Indicates that an entity operates or is situated within a particular work-related format, structure, or organizational form.
-
D.
appliedToWorkBy
Indicates that an application or request has been submitted by a person or entity for a particular job, project, or work opportunity.
-
E.
hasWorkForm
Indicates that an entity is associated with a particular form, format, or mode in which its work or activity is carried out or expressed.
- F. None of above. chosen
Provenance (4 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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69fd7b042a548190b3abe31bc3258278 |
completed | May 8, 2026, 5:56 a.m. |
Created at: April 28, 2026, 7:37 p.m.