Triple
T30972542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bohort |
E789136
|
entity |
| Predicate | oneOfFewToAchieve |
P170865
|
FINISHED |
| Object | Holy Grail vision |
—
|
NE NERFINISHED |
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: Holy Grail vision | Statement: [Bohort, oneOfFewToAchieve, Holy Grail vision]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oneOfFewToAchieve Context triple: [Bohort, oneOfFewToAchieve, Holy Grail vision]
-
A.
mustAchieve
Indicates that an entity is required or obligated to attain or accomplish a specified goal, condition, or outcome.
-
B.
canAchieve
Indicates that an entity has the ability or potential to successfully attain or accomplish a specified goal, state, or outcome.
-
C.
achievedThrough
Indicates that a result, state, or outcome is brought about or realized by means of a specified method, process, or action.
-
D.
firstToAchieve
Indicates that one entity was the earliest or initial entity to accomplish or attain a specified goal, status, or outcome before any others.
-
E.
aspiredTo
Indicates that one entity had a strong desire or ambition to achieve, become, or obtain the other entity.
- F. None of above. chosen
Provenance (4 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_69f224c4831c8190be53924ec25a150a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695f9fe7c819084322bf6cdc70a13 |
completed | May 3, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f695385a2881908cc28ef97fffc867 |
completed | May 3, 2026, 12:22 a.m. |
Created at: April 29, 2026, 8:55 p.m.