Triple
T2276410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jerusalem for Sigd celebrations |
E50780
|
entity |
| Predicate | gatheringType |
P7504
|
FINISHED |
| Object | mass pilgrimage-style gathering |
—
|
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: mass pilgrimage-style gathering | Statement: [Jerusalem for Sigd celebrations, gatheringType, mass pilgrimage-style gathering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gatheringType Context triple: [Jerusalem for Sigd celebrations, gatheringType, mass pilgrimage-style gathering]
-
A.
typeOfEvent
chosen
Indicates that one entity is classified as a specific kind or category of event.
-
B.
engagementType
Indicates the specific kind or category of engagement or interaction that occurs between the related entities.
-
C.
gatheringPlace
Indicates a location where entities come together or assemble, typically for a shared activity, purpose, or event.
-
D.
typeOfEventForStart
Indicates the specific kind or category of event that marks the beginning of something.
-
E.
activityType
Indicates the specific kind or category of action or event that an entity is engaged in or associated with.
- 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_69a88b05910c8190a9a2b1ff230c85f9 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc1ecc600819095dd4f69af1d18d8 |
completed | March 7, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69abbdb9aa3c819088d0316c5269a1c2 |
completed | March 7, 2026, 5:55 a.m. |
Created at: March 4, 2026, 7:48 p.m.