Triple
T38108271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Breton lai |
E951580
|
entity |
| Predicate | hasGenreFamily |
P70441
|
FINISHED |
| Object | medieval romance |
—
|
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: medieval romance | Statement: [Breton lai, hasGenreFamily, medieval romance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGenreFamily Context triple: [Breton lai, hasGenreFamily, medieval romance]
-
A.
genreAssociatedViaFamily
Indicates that a genre is connected to another entity through a familial or family-based relationship rather than a direct or primary association.
-
B.
hasGenreFeature
Indicates that something possesses a characteristic, element, or trait associated with a particular genre.
-
C.
hasGenreRelation
Indicates that there is an association between an entity and a specific genre, specifying the type or category it belongs to.
-
D.
hasMotherGenre
chosen
Indicates that one genre is the parent or broader category from which another, more specific genre is derived.
-
E.
hasGivenGenre
Indicates that an entity is associated with a specific genre that has been assigned or designated to it.
- 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_69f76f065ed08190bdfb1b6d817f5b39 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe78e545888190a239af1a84280fa0 |
completed | May 8, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69fe7842742081908043eb950ed69f92 |
completed | May 8, 2026, 11:56 p.m. |
Created at: May 3, 2026, 4:21 p.m.