Triple
T1410073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prevention of Insults to National Honour Act, 1971 |
E31782
|
entity |
| Predicate | typeOfSymbolProtected |
P13707
|
FINISHED |
| Object | national flag |
—
|
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: national flag | Statement: [Prevention of Insults to National Honour Act, 1971, typeOfSymbolProtected, national flag]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfSymbolProtected Context triple: [Prevention of Insults to National Honour Act, 1971, typeOfSymbolProtected, national flag]
-
A.
isProtectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
-
B.
isProtectedFor
Indicates that one entity is safeguarded or preserved specifically for the benefit, use, or rights of another entity.
-
C.
symbolType
chosen
Indicates the classification or category of a symbol based on its role, form, or function within a given system.
-
D.
hasSymbolNamedAfter
Indicates that one entity has a symbol whose name is derived from or dedicated to another entity.
-
E.
protectionType
Indicates the kind or method of protection that is applied to or associated with an entity.
- 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_69a49918e1f88190ba610f9dc8114578 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3e0bfd08190a50820bc7585c28f |
completed | March 1, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69a4bf048b648190ab77d9b45cb4855f |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.