Triple
T532250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian Administrative Service |
E12247
|
entity |
| Predicate | serviceMottoTranslation |
P1683
|
FINISHED |
| Object | Yoga is excellence in action |
—
|
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: Yoga is excellence in action | Statement: [Indian Administrative Service, serviceMottoTranslation, Yoga is excellence in action]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceMottoTranslation Context triple: [Indian Administrative Service, serviceMottoTranslation, Yoga is excellence in action]
-
A.
translationOfMotto
chosen
Indicates that one motto is a translation of another motto in a different language.
-
B.
mottoType
Indicates the specific category or kind of motto that characterizes the relationship between an entity and its motto.
-
C.
motto
Indicates that one entity serves as the guiding phrase, slogan, or maxim associated with another entity.
-
D.
mottoOriginal
Indicates that one entity is the original wording or form of another entity’s motto.
-
E.
mottoStatus
Indicates the current state or classification of a motto, such as whether it is official, proposed, historical, or otherwise designated.
- 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_69a4933208e88190891f5debab1b776d |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4985e51908190a34aa82ea9dbee1e |
completed | March 1, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69a494b3e49081909810fa417b31306f |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.