Triple
T13937095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Percival |
E335146
|
entity |
| Predicate | laterAchieves |
P1518
|
FINISHED |
| Object | understanding of the Grail mystery |
—
|
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: understanding of the Grail mystery | Statement: [Percival, laterAchieves, understanding of the Grail mystery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterAchieves Context triple: [Percival, laterAchieves, understanding of the Grail mystery]
-
A.
achievementScope
Indicates the extent or domain within which an achievement is recognized, measured, or considered valid.
-
B.
achieved
chosen
Indicates that an entity successfully reached, obtained, or accomplished a specified goal, result, or state.
-
C.
achievementStatus
Indicates the current state or level of completion of an achievement-related goal or milestone for an entity.
-
D.
placeOfAchievement
Indicates the location where an entity accomplished or attained a particular achievement or notable success.
-
E.
achievementDefinition
Indicates that one entity specifies or defines the criteria, properties, or structure of an achievement associated with another entity.
- 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_69d81c5f739081908bc05b2461f54828 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2cf42878819085146670d7b92605 |
completed | April 14, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69dbc873052c8190b33ff7f7c5a4e7ee |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:17 p.m.