Triple
T10613615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anand Sahib (first five and last pauris) |
E276064
|
entity |
| Predicate | positionWithinAnandSahib |
P94974
|
FINISHED |
| Object | first five pauris |
—
|
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: first five pauris | Statement: [Anand Sahib (first five and last pauris), positionWithinAnandSahib, first five pauris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionWithinAnandSahib Context triple: [Anand Sahib (first five and last pauris), positionWithinAnandSahib, first five pauris]
-
A.
positionInVeda
Indicates the specific location or ordering of a referenced element within the structure of a Vedic text.
-
B.
positionInTemple
Indicates the specific location or role an entity occupies within a temple.
-
C.
positionInAmidah
Indicates the specific location or order of a given element within the sequence of prayers that make up the Amidah.
-
D.
positionA
Indicates the spatial or ordered position of an entity A within a defined reference frame or sequence.
-
E.
positionInMukhyaUpanishads
Indicates the specific ordinal placement or ranking that something occupies within the sequence of the principal (Mukhya) Upanishads.
- 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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d6df5ca94c8190aa3771925913defc |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7a223c8190854409d76368f3e8 |
completed | April 8, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69d6df463ea8819091d6683e476b4f21 |
completed | April 8, 2026, 11:05 p.m. |
Created at: April 8, 2026, 7:33 p.m.