Triple
T5059105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sasak people |
E113978
|
entity |
| Predicate | riteOfPassage |
P3090
|
FINISHED |
| Object | merariq marriage custom |
—
|
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: merariq marriage custom | Statement: [Sasak people, riteOfPassage, merariq marriage custom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riteOfPassage Context triple: [Sasak people, riteOfPassage, merariq marriage custom]
-
A.
reasonForPassage
Indicates the underlying cause, motivation, or purpose that explains why a particular passage or movement occurred.
-
B.
parallelPassage
Indicates that one text segment corresponds closely in content or structure to another, such that they can be considered parallel versions or accounts of the same material.
-
C.
receivedScripture
Indicates that one entity has been given or accepted a body of sacred or authoritative religious writings from another source.
-
D.
scriptureType
Indicates the classification or category of a scripture in relation to its type or genre.
-
E.
rite
chosen
Indicates a ceremonial or ritual action performed according to established traditions or religious practices.
- 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_69bd443aa1f88190abb992d138f2cf42 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7453daac8190b2946702c6c4bd93 |
completed | March 20, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69bd715622b48190a3e8e49a5ef62b4a |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:38 p.m.