Triple
T10613192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sikh Rehat Maryada |
E276055
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | SRM |
E276055
|
NE 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: SRM | Statement: [Sikh Rehat Maryada, shortName, SRM]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SRM Context triple: [Sikh Rehat Maryada, shortName, SRM]
-
A.
SRM
chosen
SRM is the commonly used abbreviation for the Sikh Rehat Maryada, the official code of conduct and conventions for Sikhs.
-
B.
SRM-2
SRM-2 is a solid-fuel rocket motor used as the second stage of the Inertial Upper Stage to propel payloads from low Earth orbit to higher or geosynchronous orbits.
-
C.
SRM-1
SRM-1 is a solid rocket motor used as the first-stage propulsion unit for the Inertial Upper Stage space launch system.
-
D.
SRG
SRG is the IATA airport code for Jenderal Ahmad Yani International Airport serving Semarang, Indonesia.
-
E.
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.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d6df5ca94c8190aa3771925913defc |
completed | April 8, 2026, 11:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d95ecd44b08190bccbedd63544ba17 |
completed | April 10, 2026, 8:34 p.m. |
Created at: April 8, 2026, 7:33 p.m.