Triple
T11826790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vesākha |
E281277
|
entity |
| Predicate | majorActivities |
P40655
|
FINISHED |
| Object | visiting temples |
—
|
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: visiting temples | Statement: [Vesākha, majorActivities, visiting temples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorActivities Context triple: [Vesākha, majorActivities, visiting temples]
-
A.
majorActivity
chosen
Indicates that the related entity performs, participates in, or is primarily associated with a main or most significant activity.
-
B.
majorOperationsOf
Indicates that one entity is a primary or significant operation, activity, or functional undertaking associated with another entity.
-
C.
placeOfBusinessActivity
Indicates the type or nature of business activity that is conducted at a particular place or location.
-
D.
modernActivities
Indicates that the associated activities are contemporary or characteristic of the modern era, as opposed to traditional or historical practices.
-
E.
typicalActivity
Indicates that an entity is commonly or characteristically engaged in a particular activity.
- 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_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5ec3a148190bb184ba0d481b16a |
completed | April 10, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69d8a251fc08819095933f1d13c3b742 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.