Triple
T2819317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Easter Alleluia |
E54368
|
entity |
| Predicate | termOrigin |
P13656
|
FINISHED |
| Object | Hebrew Hallelujah |
—
|
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: Hebrew Hallelujah | Statement: [Easter Alleluia, termOrigin, Hebrew Hallelujah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: termOrigin Context triple: [Easter Alleluia, termOrigin, Hebrew Hallelujah]
-
A.
timePeriodOrigin
Indicates that one entity is the time period in which the other entity originated or first came into existence.
-
B.
coinedTerm
Indicates that an entity originated and introduced a particular term or expression into use.
-
C.
originallyIn
chosen
Indicates that something first appeared, was created, or was initially located within a particular context, source, or place.
-
D.
termType
Indicates the classification or category of a term within a system, specifying what kind of term it is (e.g., type, role, or function) in relation to others.
-
E.
hasAcronymOrigin
Indicates that an acronym is derived from or originates from a specific longer expression or name.
- 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_69ab49de0af08190b3da69683be1e728 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abdf15b7288190a03d1193cc0544a6 |
completed | March 7, 2026, 8:17 a.m. |
| PD | Predicate disambiguation | batch_69abdd08f2f481908c3da8a9c7a00552 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:59 p.m.