Triple
T30139117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perceval, le Conte du Graal |
E766077
|
entity |
| Predicate | firstIntroduces |
P513
|
FINISHED |
| Object | Grail into Arthurian literature |
—
|
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: Grail into Arthurian literature | Statement: [Perceval, le Conte du Graal, firstIntroduces, Grail into Arthurian literature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstIntroduces Context triple: [Perceval, le Conte du Graal, firstIntroduces, Grail into Arthurian literature]
-
A.
oftenIntroducedAs
Indicates that one entity is frequently presented or referred to by others using a particular name, title, or description.
-
B.
introduced
chosen
Indicates that one entity caused another entity to become known, presented, or brought into use for the first time to a person, group, or context.
-
C.
oftenIntroducedBy
Indicates that one entity is frequently presented, mentioned, or brought into context by another entity.
-
D.
subjectOfIntroduction
Indicates that one entity is the topic or focus being introduced by another entity.
-
E.
coIntroduced
Indicates that two or more entities jointly introduced or presented something together for the first time.
- 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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a01a9e333fc819087d583ff319be0b3 |
completed | May 11, 2026, 10:05 a.m. |
| PD | Predicate disambiguation | batch_6a01a877c9e08190b0678618d3533286 |
completed | May 11, 2026, 9:59 a.m. |
Created at: April 29, 2026, 7:17 p.m.