Triple
T25412173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indonesia Raya |
E636730
|
entity |
| Predicate | commonlyPerformedVerses |
P168029
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Indonesia Raya, commonlyPerformedVerses, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonlyPerformedVerses Context triple: [Indonesia Raya, commonlyPerformedVerses, 1]
-
A.
verses
Indicates a relationship where one entity competes or is pitted against another, as in an opposition, matchup, or comparison.
-
B.
oftenPrayedBy
Indicates that the subject is frequently the one who prays to or for the object.
-
C.
recognizesScripturesFrom
Indicates that one entity acknowledges or accepts certain scriptures as authoritative or valid based on another entity as their source or origin.
-
D.
scripturalReference
Indicates that one entity cites, alludes to, or is based on a specific passage or portion of a scriptural text found in another entity.
-
E.
receivedScripture
Indicates that one entity has been given or accepted a body of sacred or authoritative religious writings from another source.
- F. None of above. chosen
Provenance (4 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_69e75db4135881909acc287ebcb7a505 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f673633d288190b52ceb9f8a057c44 |
completed | May 2, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 21, 2026, 1:55 p.m.