Triple
T457894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yom Ha’atzmaut |
E7271
|
entity |
| Predicate | hasOfficialCeremony |
P3305
|
FINISHED |
| Object | torch-lighting ceremony at Mount Herzl |
—
|
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: torch-lighting ceremony at Mount Herzl | Statement: [Yom Ha’atzmaut, hasOfficialCeremony, torch-lighting ceremony at Mount Herzl]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOfficialCeremony Context triple: [Yom Ha’atzmaut, hasOfficialCeremony, torch-lighting ceremony at Mount Herzl]
-
A.
ceremonyType
chosen
Indicates the specific kind or category of ceremony associated with an event or relationship.
-
B.
ceremonyHeldOn
Indicates that a specific ceremony took place on a particular date or day.
-
C.
ceremonyLocation
Indicates the place where a ceremony is held or takes place.
-
D.
ceremonyNumber
Indicates the specific ordinal or identifying number assigned to a particular ceremony within a set or sequence of ceremonies.
-
E.
hasInductionCeremony
Indicates that an entity conducts or is associated with a formal induction ceremony marking the official admission of individuals into a group, role, or organization.
- 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_69a2e7e5c5bc8190a1dc8178218fba40 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efa3163081909acff040a22bd559 |
completed | Feb. 28, 2026, 1:37 p.m. |
| PD | Predicate disambiguation | batch_69a2ede614b88190be07425f5535f56d |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.