Triple
T26902473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Israel Prize for engineering |
E678068
|
entity |
| Predicate | ceremonyDuring |
P14854
|
FINISHED |
| Object | Israel Independence Day celebrations |
—
|
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: Israel Independence Day celebrations | Statement: [Israel Prize for engineering, ceremonyDuring, Israel Independence Day celebrations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceremonyDuring Context triple: [Israel Prize for engineering, ceremonyDuring, Israel Independence Day celebrations]
-
A.
ceremonyHeld
Indicates that a formal ceremony or ritual event has taken place at a particular time and/or location.
-
B.
ceremonyState
Indicates the current status or phase of a ceremony within its overall lifecycle.
-
C.
ceremonyIncludes
Indicates that a particular ceremony contains, involves, or encompasses a specified component, activity, or element as part of its structure or proceedings.
-
D.
ceremonyKnownAs
Indicates that a particular ceremony is referred to or recognized by a specific name or title.
-
E.
ceremonyTiming
chosen
Indicates the temporal relationship specifying when a ceremony occurs or is scheduled to occur.
- 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_69eee9befee48190a26f214faa867be7 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61fd623bc819091df736cf3419b99 |
completed | May 2, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 5:51 a.m.