Triple
T2526394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rehat Maryada |
E56043
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object |
SRM
SRM is the commonly used abbreviation for the Sikh Rehat Maryada, the official code of conduct and conventions for Sikhs.
|
E276055
|
NE FINISHED |
How this triple was built (4 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: SRM | Statement: [Rehat Maryada, abbreviation, SRM]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SRM Context triple: [Rehat Maryada, abbreviation, SRM]
-
A.
SRMS
SRMS is the Shuttle Remote Manipulator System, a robotic arm used on NASA's Space Shuttle orbiters to deploy, maneuver, and retrieve payloads in space.
-
B.
SRP
SRP (Stream Reservation Protocol) is an IEEE 802.1 Audio Video Bridging (AVB) protocol that enables end-to-end reservation of network resources to guarantee quality of service for time-sensitive audio and video streams over Ethernet.
-
C.
SRB
SRB is the commonly used abbreviation for Sveriges Riksbank, the central bank of Sweden and the world’s oldest central bank.
-
D.
SRB
SRB is the three-letter ISO 3166-1 alpha-3 country code assigned to Serbia.
-
E.
SRU
SRU (Search/Retrieve via URL) is a standard web-based search protocol that enables querying and retrieving information from remote databases using URLs and XML.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: SRM Triple: [Rehat Maryada, abbreviation, SRM]
Generated description
SRM is the commonly used abbreviation for the Sikh Rehat Maryada, the official code of conduct and conventions for Sikhs.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: SRM Target entity description: SRM is the commonly used abbreviation for the Sikh Rehat Maryada, the official code of conduct and conventions for Sikhs.
-
A.
SRMS
SRMS is the Shuttle Remote Manipulator System, a robotic arm used on NASA's Space Shuttle orbiters to deploy, maneuver, and retrieve payloads in space.
-
B.
SRP
SRP (Stream Reservation Protocol) is an IEEE 802.1 Audio Video Bridging (AVB) protocol that enables end-to-end reservation of network resources to guarantee quality of service for time-sensitive audio and video streams over Ethernet.
-
C.
SRB
SRB is the commonly used abbreviation for Sveriges Riksbank, the central bank of Sweden and the world’s oldest central bank.
-
D.
SRB
SRB is the three-letter ISO 3166-1 alpha-3 country code assigned to Serbia.
-
E.
SRU
SRU (Search/Retrieve via URL) is a standard web-based search protocol that enables querying and retrieving information from remote databases using URLs and XML.
- F. None of above. chosen
Provenance (5 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_69ab4a48e4f081908f1218d244608659 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd255f0d081908d20cfb812c4bfc1 |
completed | March 7, 2026, 7:23 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69af2bb0658c8190b71e1352dc4f6be3 |
completed | March 9, 2026, 8:21 p.m. |
| NEDg | Description generation | batch_69af551d68448190a076e659be28b891 |
completed | March 9, 2026, 11:17 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69af560837388190b082a8f1bee36c51 |
completed | March 9, 2026, 11:21 p.m. |
Created at: March 6, 2026, 9:46 p.m.