Triple
T36271575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D-18 |
E892686
|
entity |
| Predicate | typicalUseGenre |
P83033
|
FINISHED |
| Object | folk |
—
|
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: folk | Statement: [D-18, typicalUseGenre, folk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalUseGenre Context triple: [D-18, typicalUseGenre, folk]
-
A.
typicalGenresIncluded
Indicates that certain genres are commonly or characteristically included as part of another entity’s usual set of genres.
-
B.
usedGenre
chosen
Indicates that one entity employs or is associated with a particular genre in its creation, presentation, or classification.
-
C.
commonGenre
Indicates that two entities share at least one genre in common.
-
D.
targetGenre
Indicates the genre that something is specifically aimed at, categorized under, or intended to belong to.
-
E.
commonGenreContext
Indicates that two or more entities share a similar or related genre context, such as belonging to the same or closely related genres.
- 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_69f76e488f34819083e254dbe288c27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.