Triple
T31394675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MWV N 15 |
E800832
|
entity |
| Predicate | associatedNumberWithinGenre |
P85816
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [MWV N 15, associatedNumberWithinGenre, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedNumberWithinGenre Context triple: [MWV N 15, associatedNumberWithinGenre, 5]
-
A.
workNumberInGenre
chosen
Indicates the ordinal position or sequence number assigned to a particular work within a specific genre.
-
B.
associatedWithGenreElement
Indicates that something has a connection or linkage to a specific genre-related element (such as a motif, convention, or stylistic feature).
-
C.
referencedInGenre
Indicates that one entity is mentioned, cited, or otherwise referred to within the context of a particular genre.
-
D.
associatedWithGenreDevelopment
Indicates a relationship where something has contributed to, influenced, or been involved in the development or evolution of a particular genre.
-
E.
namedForGenre
Indicates that something is given a name based on or derived from a particular genre.
- 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:19 p.m.