Triple
T9069627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Psalm 100 |
E217331
|
entity |
| Predicate | openingWordsEnglishKJV |
P49383
|
FINISHED |
| Object | Make a joyful noise unto the LORD, all ye lands. |
—
|
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: Make a joyful noise unto the LORD, all ye lands. | Statement: [Psalm 100, openingWordsEnglishKJV, Make a joyful noise unto the LORD, all ye lands.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingWordsEnglishKJV Context triple: [Psalm 100, openingWordsEnglishKJV, Make a joyful noise unto the LORD, all ye lands.]
-
A.
openingWordsHebrew
Indicates that the specified words are the opening (initial) words of a text or passage in Hebrew.
-
B.
openingVerseTranslation
chosen
Indicates the specific translated rendering of the opening verse of a text or work.
-
C.
openingVerb
Indicates that an entity performs the initial or primary action that begins an event, process, or interaction.
-
D.
translationOfOpeningWords
Indicates that one text is a translation of the initial words or opening phrase of another text.
-
E.
openingWordsMeaning
Indicates that the meaning or significance of a text is conveyed or characterized by its opening words.
- 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_69ca83d5a7f48190b16c1e59bd43ede0 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc955d29548190a204efd3257b6d5d |
completed | April 1, 2026, 3:47 a.m. |
| PD | Predicate disambiguation | batch_69cc65f881248190bfd220bb28a9fb5f |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:11 p.m.