Triple
T33736019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laetare Jerusalem |
E864415
|
entity |
| Predicate | hasRefrainAddressedTo |
P152560
|
FINISHED |
| Object | people of Jerusalem |
—
|
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: people of Jerusalem | Statement: [Laetare Jerusalem, hasRefrainAddressedTo, people of Jerusalem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRefrainAddressedTo Context triple: [Laetare Jerusalem, hasRefrainAddressedTo, people of Jerusalem]
-
A.
hasRefrainRelatedTo
Indicates that a refrain (repeated musical or textual section) in one work is thematically or content-wise related to another specified subject or element.
-
B.
hasRefrainFunction
Indicates that something serves the role or function of a refrain, typically recurring in a structured or repetitive way within a larger context.
-
C.
containsRefrainAlsoFoundIn
Indicates that one entity includes a refrain that is also present in another entity.
-
D.
hasChorusMentioning
chosen
Indicates that a work’s chorus explicitly mentions or refers to a specified entity or concept.
-
E.
hasChorusIn
Indicates that a musical work includes a chorus section within the specified part or segment.
- 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_69f3498b24b8819096a65009e521d0e1 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:44 a.m.