Triple
T25733311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashvajit |
E645302
|
entity |
| Predicate | traditionallyPresentAt |
P117159
|
FINISHED |
| Object | Buddha’s first sermon |
—
|
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: Buddha’s first sermon | Statement: [Ashvajit, traditionallyPresentAt, Buddha’s first sermon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallyPresentAt Context triple: [Ashvajit, traditionallyPresentAt, Buddha’s first sermon]
-
A.
traditionalPresenceIn
chosen
Indicates that an entity has a customary or historically established presence within a particular place, context, or setting.
-
B.
traditionAt
Indicates that a particular tradition is practiced, observed, or associated at a specific place or location.
-
C.
traditionallyOneOf
Indicates that something is customarily or historically considered to belong to a specific set, category, or group.
-
D.
presentOn
Indicates that one entity is physically located on the surface or within the bounds of another entity.
-
E.
presentsAt
Indicates that one entity delivers or gives a presentation, talk, or performance at a particular event, venue, or occasion.
- 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_69e77e85254081908d79ee4e8715f283 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 21, 2026, 11:19 p.m.