Triple
T25259713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian flag laws |
E633268
|
entity |
| Predicate | includeProtocol |
P175190
|
FINISHED |
| Object | days when the flag is flown at half-mast |
—
|
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: days when the flag is flown at half-mast | Statement: [Indian flag laws, includeProtocol, days when the flag is flown at half-mast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includeProtocol Context triple: [Indian flag laws, includeProtocol, days when the flag is flown at half-mast]
-
A.
associatedProtocol
Indicates that one entity is linked to, governed by, or operates according to a particular protocol.
-
B.
targetsProtocol
Indicates that one entity is designed to interact with, affect, or be applied to a specific protocol.
-
C.
parentProtocol
Indicates that one protocol serves as the direct ancestor or higher-level specification from which another protocol is derived or extended.
-
D.
supportedProtocol
Indicates that one entity is compatible with, implements, or can operate using a specified communication or interaction protocol.
-
E.
targetProtocol
Indicates the communication protocol that an action, message, or connection is intended to use or be directed toward.
- 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_69e75a922ad481908f4f1f884583cb42 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6cee547108190ad3bc84297d8f516 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6cee3604c81908a07eade2f39064e |
completed | May 3, 2026, 4:28 a.m. |
Created at: April 21, 2026, 1:13 p.m.